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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful return behavior: it returns the primary document, strips HTML, and tailors output for LLM consumption. 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?

Three sentences, each earning its place: what the tool does, what it returns, and the prerequisite step. The most important scoping detail is front-loaded.

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 moderately simple fetch tool with no output schema, the description conveys the input workflow, the output nature (plain text, HTML-stripped, primary document), and the consumption use case. Parameter constraints like max_chars and cik formatting are already fully documented in the input schema.

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 coverage is 100%, so the baseline is met; the description adds value beyond the schema by explaining where the accession number comes from (edgar_recent_filings). It does not repeat parameter names or types, which is appropriate given the schema already documents them.

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 ('Fetch'), a precise resource ('text content of a specific SEC filing'), and the output format ('primary document ... stripped of HTML'), which clearly distinguishes it from sibling tools that list filings or search text. This is immediately actionable and not a tautology.

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 gives an explicit workflow: call edgar_recent_filings first to obtain the accession number. It does not enumerate alternative tools or exclusion conditions, but the primary-document/content scope makes the appropriate context clear.

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