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

Annotations only declare readOnlyHint=true, while the description adds substantial operational context: internal staff only, findings are raised by nightly checks and a weekly critic, a person decides which are worth fixing, and each finding carries a ready-made prompt with evidence and definition of done. This is rich behavioral disclosure beyond annotations and does not contradict them.

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 front-loaded with the key constraint ('Internal Coderbuds staff only') and purpose, then proceeds through default behavior and workflow. It is somewhat long but every paragraph carries useful selection or invocation guidance, with little filler.

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?

For a read-only tool with two optional parameters and no output schema, the description covers the important missing context: who can call it, what findings represent, what each result contains, the default status, and the follow-up workflow. An agent has enough information to call it correctly and avoid the main misuse case.

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 already 100%, so the baseline is 3, but the description adds meaningful context for status: accepted is the default and represents findings a person approved for fixing, while proposed findings should not be started because they are not yet agreed to be real. It does not add much for finding_id beyond the schema's 'Read one finding, whatever its status.'

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 and resource ('Read Coderbuds' self-review findings') and defines exactly what a finding is: a customer-facing statement contradicted by data Coderbuds already holds. It also distinguishes this read tool from the follow-up action tool, record-self-review-fix.

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?

It gives explicit workflow guidance: default status is accepted, work one finding at a time, fix it in this repository, open a PR, then call record-self-review-fix. It also includes a clear prohibition: do not start on a proposed finding because nobody has agreed it is real yet.

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