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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by disclosing the output components (metrics, risk changes, contradictions, source evidence, confidence) and the 'not-investment-advice flag.' It doesn't contradict annotations and provides useful context beyond the structured hints.

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 a single, dense sentence that conveys the core purpose and key elements without excessive verbosity. It is front-loaded with the tool's identity, though the 'Crucible™' branding and lengthy return list slightly reduce tightness. Overall it earns its place, but it's not maximally economical.

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?

The tool is moderately complex with 8 parameters, but schema coverage is complete and an output schema exists. The description provides a good high-level summary of inputs and outputs, and combined with schema details (like precedence notes) it is sufficiently complete for correct invocation. It could add explicit input precedence or mutual-exclusivity guidance, but this is largely covered by the schema descriptions.

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 the schema already documents all 8 parameters with descriptions. The description enumerates input modes (content, filingUrl, ticker/CIK) but does not add significant meaning beyond what the schema provides. Baseline 3 is appropriate when schema carries the parameter documentation load.

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 states the tool's purpose: 'Financial Filing Intelligence for public filings and annual reports' for specific SEC forms (10-K, 10-Q, 20-F). It distinguishes itself from sibling tools like analyze_document by narrowing scope to public filings and specifying accepted input modes (content, filingUrl, ticker/CIK).

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 implies when to use it: for public filings and annual reports, with specific forms and input modes. It does not explicitly name alternatives or exclusions, but the mention of 'SEC ticker/CIK lookup' and specific forms gives clear context. No explicit 'when-not-to-use' guidance is provided, preventing a 5.

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