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

No annotations are provided, so the description carries the full transparency burden. It discloses key behaviors: returns a list rather than a single result, does not filter server-side, and specifies the fields included in each transcript. It does not mention authentication or error cases, but for a simple read-only GET tool, this is sufficient context.

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 is three sentences, each earning its place: purpose, return value structure, and usage guidance. It is front-loaded with the main action and contains no redundant or irrelevant information.

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?

For a tool with no output schema and no annotations, the description adequately explains the return format (list with fields) and the non-filtering behavior. It could mention edge cases like no transcripts available, but the essential information for selecting and invoking the tool is present.

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?

With only one parameter (ticker) and no schema descriptions, the description compensates by stating 'by ticker,' making the parameter's purpose clear. It does not specify format or case, but the ticker symbol is a standard identifier and no further elaboration is necessary.

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 clearly states 'Get all available earnings call transcripts for a company by ticker,' using a specific verb, resource, and scope. It distinguishes itself from siblings like get_filings and search_filings by explicitly mentioning earnings call transcripts and contrasting with written SEC filings.

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 explicitly says when to use this tool: 'Use this when asked what was said on an earnings call, as opposed to in written SEC filings.' It also advises the agent on how to handle quarter-specific requests by searching within the returned list, which provides clear usage context and differentiates from alternatives.

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