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

No annotations are present, so the description must carry the full burden of behavioral disclosure. The description does not state whether the tool is read-only, whether it has side effects, what permissions are needed, or any other behavioral traits beyond the fact that it lists data.

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 and is not verbose, but it is under-specified. It could include useful details without becoming long. The conciseness is adequate, but the lack of information reduces the value of the brevity.

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 presence of three parameters, no output schema, and no annotations, the description is far from complete. It does not explain what 'mirrored pull request' means, how the filtering parameters work, or what the response looks like. The tool's complexity is not reflected.

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 only 33%, yet the description provides no additional information about any of the three parameters (npub, since_ms, dpop_token). The description fails to compensate for the missing schema descriptions, leaving the agent with no guidance on how to use the parameters effectively.

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 clearly states the verb 'list' and the resource 'every mirrored pull request for the Pull Requests register'. It is specific enough to distinguish the tool's core function, though it does not explicitly differentiate from similar sibling tools like cypher_upsert_pull_request or cypher_pr_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 to use this tool versus alternatives. There is no mention of applicable contexts, exclusions, or references to sibling tools. The agent is left to infer usage from the name alone.

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