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

Adds substantial behavior beyond annotations: describes returned fields, public PDF or ordered slide-image URLs, browser access without an API key, and explicitly notes that binary contents are not embedded. This gives the agent a clear expectation of response shape and access model.

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?

Front-loads purpose, then return details, then id source. Despite listing many fields, each sentence contributes useful information without repetition.

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 fully explains the return payload and access links. Annotations cover safety, and the description supplies the remaining calling context needed.

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 single eventId parameter is fully documented in the schema, including its source. The description repeats the same source and adds no new syntax or format meaning beyond the schema, so baseline 3 is appropriate.

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: retrieving metadata and access links for an investor-event slide deck by event id. It clearly distinguishes this metadata tool from sibling transcript and event-listing tools.

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?

Explains where to get the required eventId, naming ListInvestorEvents and GetEarningsCallEvent explicitly. It does not directly contrast with GetInvestorEventTranscript, but the use case is clear from the purpose and required id.

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