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

Beyond the readOnly/openWorld annotations, it discloses extraction methodology (a model selects the sentence or table cell, code reads the number), validation rules (unreadable figures and XBRL-disagreeing GAAP lines are dropped), quote length, filing links, and coverage limits. This is rich behavioral context and is consistent with readOnlyHint=true.

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 front-loads its purpose but is a dense, single paragraph with several parentheticals. Disclaimers such as 'Facts, not advice' and 'Quotes are the company's words' add little, and the structure could be cleaner for such a detail-heavy tool.

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?

No output schema exists, so the description must explain returns, and it does: periods, quotes, filing links, validation drops, and coverage of the last four releases. It also covers both parameters and exclusions, making it complete enough for an agent to 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%, and both parameters are already described in the schema. The description mostly repeats the limit range and id forms, adding little syntax or meaning beyond what the schema provides, 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?

The description states the tool returns forward guidance, KPIs, non-GAAP measures, and reconciled GAAP lines from the last four earnings releases for a ticker or token contract. That is a specific resource and scope, but it does not name the sibling tools (e.g., fundamentals) it should be chosen over, so it stops short of full sibling differentiation.

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 clear operational context: read once per release, and funds and foreign issuers (6-K) are not covered. It does not explicitly route the agent to an alternative when those exclusions apply, so alternatives are left implicit.

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