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

Annotations cover the safety profile (readOnly=true, destructive=false, openWorld=true), so the description's job is the extra context it supplies: IFRS companies return 404, pricing is $0.02 per call via x402 in USDC on Base, and MCP payments are Base-only. Those are real operational facts an agent must know before calling, and nothing contradicts the annotations. It stops short of describing what happens on an unknown ticker/CIK or whether the result is cached.

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 return payload is front-loaded in one dense sentence, followed by scope limits and then commercial terms. The legal/payment boilerplate ('not affiliated with or endorsed by the SEC', 'not investment advice', terms URL) is defensible for a paid x402 endpoint but does consume roughly a third of the text.

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?

There is no output schema, and the description compensates by enumerating the returned metrics, both annual and quarterly granularity, the as-of date and source link. Combined with the 404 caveat for IFRS filers and the payment mechanism, an agent has everything needed to decide and call correctly.

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 100%, so the CIK and ticker parameters are already documented, including the 'give ticker or cik' guidance. The description adds no additional parameter meaning (e.g. which wins if both are supplied, or case sensitivity), so the baseline 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?

States a specific verb+resource: key financial facts for one SEC-reporting company from EDGAR XBRL filings, and enumerates the exact metrics returned (revenue, net income, assets, liabilities, equity, shares outstanding, operating cash flow, EPS). The scope is precise enough that an agent can distinguish it from quote/price-oriented siblings like market_quote without reading the schema.

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 clause 'Company facts only' plus the US-GAAP-only restriction implies this is for fundamentals rather than prices or tokenized instruments, which partially routes against siblings. However, no sibling is named and there is no explicit statement of when not to use it (e.g. for IFRS filers, use X instead), so guidance is implied rather than stated.

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