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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description only needs to add context. It adds the SEC XBRL companyfacts API as the source and notes the tool is free, which is useful. However, it does not discuss data limitations, units, or the shape of returned periods, leaving a moderate gap.

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 compact sentences with no filler. The action and resource are front-loaded, the key metrics are listed in a readable series, and period selection plus free/source context are added efficiently. Every clause 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 simple read-only tool with strong annotations, the description plus schema defaults and enums provide enough to call it correctly. The absence of an output schema is mitigated by the metric list, though minor ambiguity around 'limit' and return structure remains.

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 only 33%, so the description partially compensates by explaining period values (annual = 10-K, quarterly = 10-Q) and listing the kind of metrics returned. It does not clarify the meaning of 'limit' (e.g., number of periods vs. number of tags) or ticker formatting, so parameter understanding is incomplete.

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 action ('parsed from SEC XBRL filings') and a specific resource (headline financial statements), listing concrete metrics and the annual/quarterly distinction. It is clear and actionable, though it does not explicitly distinguish itself from sibling tools like equities_filings or equities_concept.

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 the tool is for summary fundamentals via 'headline financial statements' and 'curated tags,' but it never states when to use it over alternatives or when not to use it. There is no mention of sibling tools or exclusions, leaving the agent to infer routing.

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