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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds genuinely non-obvious behavior: identity resolution rules (trusted resolutions show real names; unverified voices degrade to a role label or neutral speaker number) and speaker-turn ordering. It omits any statement about pagination ceiling behavior on longer calls.

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, front-loaded with what the tool returns and followed by the attribution caveat and the prerequisite. Dense but every sentence carries information; no padding.

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?

With no output schema, the description properly explains what the return content looks like (ordered speaker turns with attribution). For a 5-parameter read tool with full schema coverage and safe annotations, this is close to complete, only missing explicit guidance on long-call pagination.

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 schema already documents ticker format, limit clamping, offset paging, and the fiscal-year/quarter omission semantics. The description adds no parameter detail 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?

States a specific verb and resource ('speaker-labelled transcript of a company's earnings call for a fiscal quarter') with added scope detail about ordering and attribution. This clearly distinguishes it from GetEarningsCallEvent, GetEarningsCallToneAndThemes, and GetInvestorEventTranscript.

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?

Explicitly routes the agent: 'Use GetEarningsCallEvent first to check a transcript exists.' That is a real prerequisite, not implied. It does not, however, state when to prefer this over GetInvestorEventTranscript, so it stops short of full alternative coverage.

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