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

No annotations are provided, so the description carries the full burden. '(large)' is a genuinely useful disclosure about payload size and performance cost that goes beyond the schema, but nothing is said about rate limits, permissions, result format, or whether filtering by period/concept is possible.

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?

A single tight sentence with no filler, and the key caveat '(large)' is placed immediately at the end. It is efficient, though terse enough that it borders on under-specification rather than pure conciseness.

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 one-parameter read tool with no output schema, this is minimally adequate: it says what is returned and that it is large. It omits any indication of structure (facts per period/concept), whether the response is paginated, or how to avoid pulling an unmanageable result 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?

There is one parameter, and schema description coverage is 100% ('ticker or CIK' already documented in the schema). The description's 'a company' adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 names a specific verb+resource: retrieving every XBRL fact a company has reported. It is unambiguous about what the tool returns, distinguishing it from generic filing tools. However, it does not differentiate itself from siblings like xbrl_to_json, which an agent could reasonably confuse with a raw XBRL fact dump.

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?

There is no guidance on when to use this versus xbrl_to_json, financial_statements, or full_text_search, nor any stated prerequisites. The parenthetical '(large)' is the only signal, hinting that this is a heavyweight call, but it is not framed as a usage condition.

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