Document Summary

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

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add context. It does, by enumerating the returned digest fields and the 'ONE filing' scope, but says nothing about auth requirements, rate limits, or behavior when the filing has not been parsed.

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 dense sentences, front-loaded with what is returned and following immediately with how to select a document and which sibling to use instead. Every clause carries information; no filler.

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?

With no output schema, the description appropriately enumerates the digest contents and the PDF/Markdown links, and annotations carry the safety profile. An agent has enough to select and invoke it correctly against a crowded sibling set.

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 3. The description reinforces the doc_id-vs-doc_type precedence and where doc_id comes from, but this largely repeats the schema, and it never mentions the symbol/ticker/identifier alias parameters that make up three of the five inputs.

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?

States a specific verb and resource: an 'investor digest of ONE parsed filing' returning summary, highlights, risks, guidance, key metrics and links. It explicitly distinguishes itself from the sibling that returns raw text by naming read_document.

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?

Gives explicit routing conditions: pass doc_id sourced from list_company_documents, or doc_type to get the newest of that type, and redirects to read_document or links.markdown_url when the caller actually wants the text. When-to-use and the alternative tool are both named.

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