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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states it 'reports' but does not clarify if the operation is read-only, requires authentication (e.g., dpop_token), or has side effects. The agent lacks insight into permissions, idempotency, or resource impact.

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 a single sentence, concise but at the expense of clarity. It front-loads the purpose but uses domain-specific terminology without elaboration. It could be restructured to include more information without sacrificing conciseness.

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?

Given the tool has 2 optional parameters, no output schema, and no annotations, the description is too sparse. It does not explain the return value, expected behavior with missing parameters, or how the 'grep-scope shrinkage' metric is derived. The agent lacks sufficient information to use the tool reliably.

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 0%, and the description does not explain the two parameters (npub, dpop_token) at all. The agent cannot infer their meaning, expected format, or whether they are optional (defaults to empty string). This is a critical gap for correct invocation.

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 states it reports how issues were located to measure grep-scope shrinkage, which is a specific verb-resource pairing. However, 'issues' and 'grep-scope shrinkage' are jargon not explained, making the purpose somewhat vague for an AI agent. It is not a tautology but lacks clear connection to the tool's domain.

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?

No guidance is provided on when to use this tool versus sibling tools like cypher_adoption_status or cypher_check_balance. The description does not mention prerequisites, alternatives, or exclusions, leaving the agent without context for appropriate invocation.

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