get_slideshow

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

No annotations provided, so description must carry full burden. It states 'Read-only — consumes no quota' and explains that download links may be empty if no export file exists (e.g., Telegram-only export). This clearly discloses mutation behavior, quota impact, and edge cases.

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?

Description is concise with three front-loaded sentences. First sentence states core functionality, second gives usage guidance, third adds caveat. No filler; every sentence earns its place.

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?

Tool has one parameter, no output schema, and low complexity. Description covers purpose, usage, behavior, parameter meaning, and edge cases (empty download links). Complete for the context.

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 100% with id parameter described as 'The slideshow id (uuid). Get it from list_slideshows.' Description adds extra context by reiterating where to get the id, adding value beyond the schema, justifying a score above baseline 3.

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?

Description clearly states 'Fetch one slideshow by its id, including fresh 1-hour signed download URLs for its export ZIP.' This specifies the verb, resource, and distinct value (fresh 1-hour links), distinguishing it from siblings like generate_slideshow and list_slideshows.

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?

Provides explicit usage scenarios: 'when the user asks to get the download link for slideshow X, re-download a slideshow, or get the link again.' Also mentions prerequisite ('Get the id from list_slideshows first') and clarifies that links from generate_slideshow expire after 24h, while this mints fresh 1h links.

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