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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the rest and does so well: it discloses the upstream source (FFIEC Call Report Schedules RI, RC, RC-K), the unit conventions ($000s for dollars, percentages for ratios), and that line items are tagged with Schedule RI items and MDRM codes. It does not discuss rate limits, data latency, or behavior when data is missing for a quarter.

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?

Front-loaded with the core purpose in the opening clause, then source and unit disclaimers at the end. It is a single dense sentence that verges on a run-on list, but every clause carries information an agent would otherwise have to guess.

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?

Three parameters, no output schema, and a read-only analysis tool: the description supplies the analytical content, the data provenance, and the unit conventions, which is enough for correct invocation. Only the absence of explicit routing guidance against sibling analysis tools keeps it short of full completeness.

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 each parameter is documented, so the baseline would be 3; the description nudges higher by tying 'history' to the quarters range and 'peers' to the peer comparison, plus the units note clarifies how returned dollar figures should be read. It still adds no formatting details for the comma-separated peer list beyond the schema.

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?

Names a specific analysis and enumerates its components: each income statement line's share of average assets, contribution to ROA, leverage on equity, three-factor view, and attribution of ROE movement. It is clearly a DuPont-style profitability decomposition, though it never names a sibling to contrast with.

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?

Implies the research use case through 'history and peers,' which maps loosely to the quarters and peers parameters, but gives no explicit when-to-use or when-not-to-use guidance relative to siblings like margin_analysis, peer_analysis, or common_size. The agent must infer the boundary.

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