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

With no annotations provided, the description carries the full burden. It discloses the read-only nature via 'Retrieve' and specifies the return value (list of companies with transcript counts), adding useful context. However, it omits any details about authentication, rate limits, pagination, or data scope, which would be valuable for a zero-parameter API call.

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 two sentences and mostly front-loaded, but contains slight redundancy with 'earnings transcripts' repeated. It is still efficient and each sentence contributes to the purpose.

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?

Given there is no output schema, the description explains the high-level return value (list of companies with counts). For a zero-parameter tool, this is fairly complete. It could mention specific fields or any limits, but the core information 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?

The input schema has zero parameters, so the baseline is 4. The description doesn't need to explain parameters, and it correctly references 'for companies' without implying any filterable inputs.

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 the tool retrieves a list of companies with available earnings transcripts and includes a count of transcripts per company. It uses specific verbs ('Access', 'Retrieve') and names the resource ('Earnings Transcript List API'), distinguishing it from sibling tools like getEarningsTranscript or getEarningsTranscriptDates.

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 the tool is for when you need an overview of companies that have earnings transcripts and their counts, but it does not explicitly state when to prefer this over alternatives like getAvailableTranscriptSymbols or getLatestEarningsTranscripts, nor does it mention any exclusions.

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