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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the two return modes (missing-research list, or the scoring anchors and governance ceiling the evidence sets), which tells the agent what downstream effect the call has. It does not explain the lifecycle of the passed-back `record` token, and the phrase 'Adds ... to the work record' sits in mild tension with readOnlyHint=true, though in a stateless token-passing workflow that is reconcilable.

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?

Two sentences, front-loaded with the action and zero filler words. The only weakness is that the second sentence compresses two distinct return modes into a single 'or' clause, which is terse to the point of mild ambiguity about which mode triggers when.

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 carries the burden of describing returns, and it does give a partial picture (missing research, or scoring anchors plus governance ceiling). It leaves out whether the updated record token is returned for the next workflow step, error behavior, and the 20-finding limit, which are gaps for a tool whose output feeds a scoring workflow.

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%, at the baseline threshold, and the schema already documents `record` fully. The description does add meaning for the finding payload by naming source, quote and confirmation status, but it is silent on the enum-constrained fields that matter most (item, effect, control, status values, searches) and on the maxItems=20 cap. It compensates only partially for the coverage gap.

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 gives a concrete verb and resource: it adds research findings, each carrying a source, quote and confirmation status, to the work record. That is far more specific than the title alone and lets an agent distinguish it from assess_and_decide or record_answers. It stops short of explicitly contrasting itself with those siblings, so it lands at a strong 4 rather than 5.

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?

There is no explicit 'use this when / do not use this when' statement and no sibling is named as an alternative. The clause 'Returns the required research still missing' does imply the tool sits in an iterative gather-until-complete loop, which is usable context, but the agent must infer it. This is implied usage rather than stated guidance.

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