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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is given. The description adds valuable behavioral detail: it returns metadata and access paths, not the binary contents, and explicitly lists the response fields including the distinction between PDF and image-slideshow paths. This goes beyond annotations by explaining what the response contains and what it does not.

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 a single, well-structured paragraph that front-loads the purpose and then details the return fields. It avoids redundancy and each clause adds information, but it is slightly longer than necessary and uses a semicolon-heavy structure. Still, it is efficient and easy to parse.

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 compensates by listing all returned metadata fields and the two possible path types. It also clarifies that binary content is not embedded, which prevents an agent from expecting it. The prerequisite for the id is explicitly stated. This is complete for an agent to call the tool correctly.

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 parameter eventId is fully described in the schema with the same source guidance ('from ListInvestorEvents or GetEarningsCallEvent'). Since schema description coverage is 100%, the baseline is 3; the description does not add additional semantic meaning beyond what the schema already provides.

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 it 'Get[s] metadata and access links for a captured investor-event slide deck by event id,' specifying the resource and action. It distinguishes itself from sibling tools like GetInvestorEventTranscript by detailing the exact fields returned (deck metadata, PDF vs. image-slideshow kind, page count, etc.) and by noting that binary content is not embedded, making its purpose unambiguous.

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 provides clear context on how to obtain the required event id ('Get the event id from ListInvestorEvents or GetEarningsCallEvent'), which serves as a prerequisite. It implies this tool is the one for slide-deck metadata, distinct from transcript tools, though it does not explicitly list alternatives or exclusions. This is clear contextual guidance without explicit 'when not to use' phrasing.

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