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

No annotations are provided, so the description must carry the full burden. It indicates a read-only fetch (no side effects implied) but does not disclose authentication requirements, rate limits, what happens if the issue doesn't exist, or any other behavioral traits. The description is adequate for a simple fetch but lacks depth.

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 that is concise and front-loaded with the verb 'Fetch'. While it could be slightly more informative (e.g., clarifying what 'provenance chain' contains), it communicates the core action efficiently with no wasted words.

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?

There is no output schema, so the description must explain what the tool returns, but it only vaguely lists 'GitHub URLs, fix PRs, and provenance chain'. It does not specify the data structure, whether the URLs are clickable (though implied), or any error indicators. For a 4-parameter tool with no output schema, this is insufficient.

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 50% (only repo_name and issue_number have descriptions). The tool description adds no additional meaning for any parameter. It does not explain the purpose of npub and dpop_token (both have defaults but no description), nor does it clarify expected formats. The description fails to compensate for the missing parameter 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?

The description uses a specific verb 'Fetch' and clearly identifies the resource: 'an issue's GitHub URLs, fix PRs, and provenance chain'. It distinguishes itself from sibling tools like cypher_list_issues (which lists issues) and cypher_pr_provenance (which focuses on PR provenance) by specifying 'issue's...fix PRs' and 'for browser click-through', implying returning actionable URLs.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, context for when to prefer it over cypher_list_issues or cypher_pr_provenance, nor any exclusions. The usage context is only implied by the tool name and description.

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