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

The annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context: ticker/name/CIK resolution, default substantive-form filtering, 'financials_status: unavailable' with a reason instead of an error, and stale-concept handling. It clearly discloses what the tool does and does not return beyond the 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 long but densely packed and front-loaded with the one-call value proposition. Every sentence earns its place: scope, defaults, alternatives, aliases, error behavior, and drill-downs are all covered without repetition or 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 and a complex multi-part return, the description compensates by enumerating the identity fields, filing list fields, and financial metrics, and by covering the no-XBRL edge case. It is complete enough for an agent to call the tool and interpret the result without needing to guess.

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% and the description adds value beyond it: explaining that `ticker_or_cik` accepts ticker, name, or CIK; that `form_type` can be a single form or 'all'; and that financial metrics are resolved to the filer's current reporting concepts. Aliases are explicitly clarified as equivalent spellings used by sibling tools.

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 uses a specific verb ('returns') and names the exact resource ('SEC picture on $TICKER'), explicitly enumerating the three outputs: identity, filings list, and XBRL figures. It distinguishes itself from the chain of edgar_ticker_to_cik -> edgar_company_filings -> edgar_company_concept and from sibling tools, making selection unambiguous.

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?

It gives explicit when-to-use framing ('ONE CALL for...'), names the manual chain it replaces, and provides concrete routing guidance for drill-downs (edgar_filing_text, edgar_company_concept, edgar_company_facts) and the cross-source alternative (entity_profile). This is the strongest possible usage guidance.

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