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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'earnings call schedules based on fiscal year and quarter' which hints at the data included, but it does not specify the return format, whether historical or future dates are included, or any pagination/ordering behavior. This is insufficient for a tool with zero annotation coverage.

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 front-loads the primary purpose: 'Access earnings call transcript dates for specific companies'. The second sentence adds context about fiscal year/quarter but does not waste words. It is appropriately concise for the tool's simplicity.

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?

The tool is simple (one parameter, no output schema), but the description does not fully explain what the response contains. While it mentions 'dates' and 'fiscal year and quarter', it leaves unclear whether the output is an array, includes all historical quarters, or requires additional parameters. The lack of annotation and output schema makes the description the only source of context, and it is not sufficient.

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% (the only parameter 'symbol' has a description 'Stock symbol'). The tool description adds no additional semantic detail about the parameter beyond what the schema already provides, so the baseline score of 3 applies as the description does not compensate or conflict.

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 fetches earnings call transcript dates for a given company symbol, referencing the 'FMP Transcripts Dates By Symbol API'. This distinguishes it from siblings like getEarningsTranscript which retrieves actual transcript content. The phrase 'comprehensive overview of earnings call schedules' adds context but is slightly vague about the exact output.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies usage 'for specific companies' but does not mention when to prefer this over getEarningsTranscript, getEarningsTranscriptList, or getEarningsCalendar. No exclusions or alternative tool names are provided.

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