Drupal 7 Module Development

Drupal Permissions and Security
3. An optional description of the permission. This string should be a complete
sentence, and wrapped in t(). Drupal's user interface guidelines encourage
you to use this element if the permission needs special clarification,
especially if permission is being given to untrustworthy users who could
pose a security risk. For our example, we will clearly state: "Displays the
content types that a user may create on the user's profile page."
When we put these three parts together, our hook looks like the following code:
/**
* Implement hook_permission().
*/
function example_permission() {
return array(
'view content creation permissions' => array(
'title' => t('View the content creation options for registered
users'),
'description' => t('Displays the content types that a user may
create on the user\'s profile page.'),
),
);
}
Using the description element is tempting, for completeness, but
Drupal's UI testing discovered that it serves mostly a visual clutter for the
end user.
The following screenshot shows examples of the types of permissions that
benefit from a full description. This page can be found at the following path:
admin/people/permissions
[ 220 ]