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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-behavior ('does not execute the analysis or transfer local raw files'), but omits what the call actually produces (a request handle? a receipt?) and never mentions that repeat calls are not idempotent per idempotentHint=false.

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 followed by the key exclusion; nothing is padded. The density of undefined terms costs readability but not length.

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 five-parameter, zero-coverage, no-output-schema tool this is thin. An agent cannot learn what the prepared request looks like, how rigor affects rigor of validation, or how the digest bindings are supplied, so it may call the tool without the information the call conceptually requires.

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% across five parameters, so the description must carry the burden and does not. It never explains rigor's three levels, the difference between requiredOutputs and requestedWork, or where the referenced digests come from - in fact it names digests that are not parameters at all, which invites confusion.

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 states a specific verb and resource ('Prepare a rigorous specialist execution request') and enumerates the binding context (project, ResearchContext digest, capability authority, artifact digests). It is distinguishable from validate_specialist_receipt by the 'does not execute the analysis' boundary, though the dense jargon ('capability authority') clouds the plain action.

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 when-to-use guidance and no named alternatives among the many siblings (validate_specialist_receipt, researchpilot_capabilities, text_analysis_pilot). The only routing signal is a negative one ('does not execute'), which hints at a preceding step without naming it.

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