Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the safe read-only nature is covered. The description adds only the upstream endpoint (GET /api/v1/permissions) and nothing about pagination behavior, ordering, or result size, which is the more useful missing context for a cursor-paginated list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the resource scope front-loaded ahead of the endpoint reference. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only paginated list with no output schema and three optional parameters, the description is adequate but thin. It never tells the agent that results are paged via next_token or what a permission entry contains, information an agent would need to chain calls correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so sort, page_size, and next_token are fully documented in the schema itself. The description adds no syntax or format hints beyond that, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (permissions) with scope ('defined in the business'), which separates it from kinde_list_role_permissions and create_permission. It stops short of explicitly naming the sibling it differs from, so an agent must infer the business-level vs role-level distinction from phrasing alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'defined in the business' implicitly signals the business-level permission catalog as opposed to role-scoped permissions, giving an implied use case. However, there is no explicit when-to-use, when-not-to-use, or named alternative, leaving the choice between this and kinde_list_role_permissions to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.