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

No annotations provided, so description carries full burden for behavioral disclosure. It mentions only 'show', implying a read-only operation, but does not confirm safety, idempotency, or required permissions. No disclosure of whether the tool has side effects or authorization needs.

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?

Single sentence, no redundant information. Could be improved by separating purpose from usage guidelines, but still efficient.

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?

No output schema provided, but description doesn't explain return format. Required parameters are listed, but no mention of prerequisites or permissions. Adequate for a read tool but lacks full completeness.

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 coverage is 50% (only repo_name and issue_number have descriptions). The description adds 'which repos' and 'issue' context but does not explain undocumented parameters npub and dpop_token. Fails to compensate for missing schema descriptions.

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?

Description clearly states the tool shows which repos declined an issue and why, with specific verb 'show' and resource 'repos that have declined an issue'. It effectively distinguishes from siblings like 'cypher_route_rejection' or 'cypher_note_rejection' which are about performing rejections, not viewing history.

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?

Description implies usage for viewing decline history, but does not explicitly state when to use this tool versus alternatives like 'cypher_route_rejection' or 'cypher_note_rejection'. No guidance on exclusions or prerequisites.

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