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

Annotations already declare write/atomic-idempotent/non-destructive/open-world, and the description adds genuinely new behavior: authorization gating, atomic application semantics, terminal one-shot submission, the legacy-shim acceptance path, and the domain rule 'Web research is NEVER an executed PASS.' Those details materially change how an agent prepares and times the call.

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?

Five dense sentences with the prerequisite and the preferred input shape front-loaded and zero filler. The middle sentence is long and field-list heavy, but every sentence carries actionable information.

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 9-parameter tool with a nested pack and an output schema, it covers what to send, who may send it, and that submission is terminal. Gaps remain around result_type selection (six enum values unmentioned) and what target_recommendation is for, which is notable given the low schema coverage.

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?

With only 44% schema description coverage, the description compensates by enumerating the preferred canonical pack fields (candidate_action, applicability, steps, limitations, obsolete_approaches, negative_results, evidence_boundary, what_remains_unknown) and the S1..Sn source-id convention, plus warning that the flat guidance/applicability/limitations params are shims. It leaves target_recommendation and the result_type enum semantics unexplained.

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 specific verb and resource: 'Atomically applies supported guidance or source evidence to the claimed gap.' That clearly separates it from claim_research_job, get_research_job, and record_outcome in the sibling list, and the opening 'Enrolled researchers only' establishes the actor scope up front.

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 supplies a clear usage context: only enrolled researchers, only for a claimed gap, and 'One terminal submission then stop' tells the agent not to retry or loop. It never names an alternative tool or an explicit when-not condition (e.g. what to do instead if the job is not claimed), so it stops short of full routing guidance.

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