Show Permission Manifest

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

Annotations already indicate read-only and idempotent behavior. The description adds value by specifying the return format (paginated JSON array) and pagination controls (page, per_page). It also differentiates between company and project levels in parameter descriptions, providing context beyond annotations.

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?

The description is concise at three sentences, front-loading the purpose. The final sentence referencing the specific API endpoint may be slightly extraneous but does not detract significantly. Overall, it is appropriately sized.

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?

The tool is simple with well-documented parameters and annotations. The description covers purpose, pagination, and level context. However, without an output schema, more detail on the returned structure could be helpful. It is adequate but not rich.

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 the baseline is 3. The description does not add significant meaning beyond what is already in the schema; it mentions pagination parameters which are also documented in the schema. No new parameter semantics beyond schema.

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?

The description clearly states the tool retrieves a permission manifest for the current user, providing a verb+resource description. It distinguishes itself from sibling tools by focusing on permissions, but the mention of 'a specific Users & Permissions by its identifier' is slightly vague as the actual parameters are project_id and company_id.

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 description gives a general usage directive ('Use this to fetch the full details...') but lacks explicit guidance on when to use this tool versus alternatives, such as other user or permission listing tools. No exclusions or when-not-to-use scenarios are mentioned.

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