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

With no annotations and a description that only says 'Pivot to a service', there is no disclosure of behavioral traits such as read/write nature, side effects, authentication requirements, or rate limits. The agent has no information on what happens when the tool is invoked.

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 very concise but at the expense of clarity. It consists of one short sentence that fails to convey essential information, making it under-specified rather than efficiently concise.

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 three parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain return values, required context, or how this tool fits into a workflow with many siblings.

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 only 33% (only repo_name has a description). The tool description does not explain any of the three parameters (npub, repo_name, dpop_token) or their roles. The agent cannot infer how to use the parameters beyond their types and defaults.

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 'Pivot to a service — its capabilities, symbols, and issues.' uses the vague verb 'pivot' and does not clearly specify the action. It gives a general idea of the tool's focus but lacks precision, making it harder for an AI agent to understand what exactly the tool does compared to siblings like cypher_issue_provenance.

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 or when not to use this tool. There is no mention of alternatives or prerequisites, leaving the agent without context for appropriate usage.

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