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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it returns an audited deliverable and that inputs are validated server-side, but does not detail behavior such as async handling or limitations. This is adequate but not rich.

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?

Three sentences, efficient, no redundant text. The first sentence is a bit jargony but acceptable. Reference case is useful.

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?

Tool has nested objects and 6 parameters with no output schema; description is too brief to guide the agent on constructing nested fields or understanding what the deliverable contains. Async parameter and other nuances are left unexplained.

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 17% (async alone). The description mentions transcript and 10-Q/guidance as inputs, mapping loosely to transcriptExcerpt and secFilingContext, but does not explain the structure of company or quarter objects, nor analystFocus. It relies heavily on field names, which is insufficient for low coverage.

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 identifies the tool as an Earnings Reviewer that returns a structured, audited deliverable for fundraising, with a reference case showing transcript + 10-Q + guidance → analyst note. The purpose is clear (analyze earnings and produce an analyst note) but it does not explicitly differentiate from sibling tools like earnings_transcript_signals.

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 use for fundraising-focused earnings analysis but provides no explicit when-to-use vs alternatives or exclusions. The reference case gives context but no decision guidance.

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