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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it lists privileges no role grants yet (completeness of the listing), notes that role capability is only the app's default until read here, and warns that a privilege rule matches the whole key ('REPORTS_VIEW' does not match REPORTS_VIEW_ALL').

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?

Purpose and routing are front-loaded, which is good, but the description drifts into app-design guidance not needed to invoke the tool ('never with a hard-coded role check in app code') and a somewhat cryptic line about defaults. Roughly a third of the text does not help an agent select or call this tool.

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 one-parameter read tool with no output schema, the description covers purpose, return fields, sibling differentiation, and downstream workflow use. Nothing an agent needs to call it correctly is missing.

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?

Only one optional parameter (app) and schema description coverage is 100%, so the schema already documents the omit-to-use-current-app behavior. The description adds nothing about the parameter beyond what the schema provides, so the baseline 3 applies.

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 and resource ('List every privilege defined for the Bridge app') and enumerates the returned fields (id, key, description). It explicitly separates itself from the closest sibling by noting 'list_roles shows which privileges each role grants.'

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?

Gives explicit trigger conditions and named alternatives: 'Use this before create_role / update_role, before gating a flag rule on a privilege, or to find the key for update_privilege or delete_privilege.' Nothing is left to inference about when this tool is the right pick.

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