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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool fetches data (read operation) but does not mention any side effects, permissions required, or data limitations (e.g., whether it only works for PRs already linked via cypher_link_pr). It is a simple read, but the lack of detail on what 'fixes' and 'intentions' entail leaves gaps.

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 and front-loaded with the primary action. No fluff, but it could be slightly longer to elaborate on the output nuance without becoming verbose.

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's purpose (fetching provenance for PRs) and the absence of an output schema, the description provides sufficient high-level information but lacks important context: what constitutes 'fixes' and 'intentions', whether the tool returns structured data or expects pre-existing links, and how it interacts with related tools like cypher_upsert_pull_request. The sibling list is large, so more context on how this fits into the workflow would be helpful.

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% with only two of four parameters described (number and repo_name). The description does not explain the purpose of npub and dpop_token, which are optional but have defaults. For a security/identity tool, these params likely carry auth context, but the description gives no hint. The description adds little beyond the schema's existing 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 'Fetch a PR's fixes and the intentions it enforces for the PR dossier' clearly states the action (fetch) and the resource (PR) with a specific scope (fixes and intentions). It distinguishes from siblings like cypher_upsert_pull_request and cypher_link_pr by focusing on retrieval of provenance details, though it could be more explicit about the unique output.

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?

The description implies a use case (fetching provenance for a PR dossier) but does not provide explicit guidance on when to use this tool versus similar audit or provenance tools (e.g., cypher_issue_provenance, cypher_invariant_provenance). It lacks exclusions or alternative suggestions.

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