get_presentation

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

No annotations provided, but description indicates read-only behavior via 'presentations.readonly OAuth scope.' Details that it returns slide objectIds needed by other tools, providing helpful behavioral context without contradicting any annotations.

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?

Three concise, front-loaded sentences with no unnecessary words. Each sentence adds value: purpose, return value relationship to other tools, and scope requirement.

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 output schema exists, description adequately covers context: read-only scope, return information linking to other tools, and alternative tools for specific needs. No gaps.

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 covers 100% of parameters with descriptions; the description adds no additional semantic detail beyond what's already in the schema. 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?

Clearly states verb 'retrieve' and 'extract' with specific resource 'presentation's structure and text per slide.' Distinguishes from sibling tools like get_page and get_page_thumbnail by specifying its broader scope.

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?

Explicitly tells when to use this tool vs alternatives: 'For a single-slide deep dive use get_page. For a rendered thumbnail image use get_page_thumbnail.' Also mentions required OAuth scope.

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