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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to repeat safety. The description adds value by explaining the return fields (metrics, risk changes, contradictions, source evidence, confidence, not-investment-advice flag) and the input precedence (content > filingUrl > ticker lookup). No contradiction with annotations.

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 extremely concise at two sentences, with no filler. It front-loads the tool's brand and purpose, then efficiently lists inputs and outputs. Every sentence earns its place.

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 tool with 8 optional parameters and no required ones, the description covers the main input patterns and output fields. The output schema exists to detail return values. Minor gap: it does not mention that year and form default to latest, but overall it is sufficiently complete for an AI agent to understand the tool's capabilities.

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 100%, so baseline is 3. The description adds value by explaining the precedence of input methods (content first, then filingUrl, then ticker/CIK) and the accepted form types, which is not in the schema. This helps the agent understand how to choose among the many optional parameters.

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 clearly identifies the tool as 'Crucible™ Financial Filing Intelligence for public filings and annual reports'. It specifies the accepted input methods (content, filingUrl, ticker/CIK) and the specific filing forms (10-K, 10-Q, 20-F), which distinguishes it from the sibling tool 'analyze_document' that handles general documents.

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 explicitly states the tool is for public filings and annual reports, and lists the accepted input methods, giving clear context for when to use it. However, it does not explicitly mention when not to use it or name alternative tools, but the specificity of financial filings makes usage clear.

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