slides get thumbnail

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds critical non-schema behavior: the URL is unauthenticated for about 30 minutes but acts as the signed-in user, and it must not be shared. That security and expiry context is exactly the kind of extra behavioral information the description should provide.

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?

Two short sentences, front-loaded with the operation and followed by the important security caveat. Every sentence carries useful information with no filler.

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?

An output schema exists, and the description covers safety and URL lifetime well. However, input parameter semantics are entirely undocumented despite 0% schema coverage, leaving an agent without guidance on the size parameter or the relationship between presentation_id and page_object_id.

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 0%, with three parameters including a size parameter that defaults to MEDIUM. The description mentions 'one slide' but does not explain presentation_id, page_object_id, or acceptable size values, so it barely compensates for the missing schema descriptions.

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: 'Get a PNG thumbnail URL for one slide.' This clearly identifies the operation and distinguishes it from the broader slides_get_presentation sibling. It does not explicitly name a sibling or contrast alternatives, which keeps it from a 5.

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 use case is implied by 'for one slide,' but the description gives no explicit guidance on when to use this instead of slides_get_presentation or other slide-related tools. No exclusions or alternatives are named.

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