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

With no annotations, the description carries the burden and does well: it discloses that reads use no credits, that source/code/comment content should be treated as data rather than instructions, and that a draft or passing CI is not proof of production safety. It lacks auth/rate-limit details but provides meaningful behavioral context.

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?

Four sentences with the main purpose front-loaded, followed by parameter guidance and behavioral caveats. Each sentence adds operational value; it is slightly dense but not padded.

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?

The description provides strong coverage of safety, cost, and content scope for a simple read tool. However, with no output schema and no explanation of the required id parameter, the agent still lacks complete invocation details and return-shape hints.

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%, so the description must compensate. It explains includeCurrentPr well ('read the bounded current GitHub PR diff with freshness/completeness metadata'), but it never defines the required id parameter, leaving the agent to infer it is a repair identifier.

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 opens with a specific verb, 'Read,' and enumerates precise resources: captured external evidence, affected code, immutable patch versions, individual CI checks, and repair decisions. This clearly identifies the tool as a detail-inspection operation for a repair, distinguishing it from sibling tools like list_repairs.

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 gives clear operational context: set includeCurrentPr to retrieve the bounded GitHub PR diff, and reads consume no model or repair credits. It does not explicitly name alternatives or state when not to use this tool, so it stops short of a 5.

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