get_presentation

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

With no annotations, the description carries the full burden. It explains default behavior (trimmed summary), the raw option, and that it uses 1 API call to keep output bounded. However, it does not explicitly state read-only nature or authorization needs, though 'Get' implies read.

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 concise with about six sentences, front-loaded with the main purpose, followed by a note on the bounded output and then the parameter list. Every sentence adds value without redundancy.

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 no annotations and an output schema present, the description adequately covers the tool's behavior and parameters. It explains the summary vs raw behavior and the bounded output. It could explicitly mention read-only or auth requirements, but overall it is mostly complete for an agent to decide usage.

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 coverage is 0%, so description must document parameters. It provides brief but meaningful descriptions for all three parameters: presentation_id ('The presentation ID'), include_masters ('Also summarize layouts and masters'), and raw ('Return the full, untrimmed API response instead of the summary'). This adds value beyond the schema.

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 a presentation as a bounded, structured overview', specifying a specific verb and resource. It distinguishes from siblings by emphasizing the trimmed, summarized nature, contrasting with raw or other tools like get_page or list_slides.

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 context on when to use the raw parameter for full output versus the default summary, but does not explicitly compare to sibling tools like get_page or list_slides, or mention when not to use this tool.

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