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

Annotations are minimal (readOnly=false, destructive=false, idempotent=false), so the description carries the burden and does so richly: ticket expiry of 15 minutes, single-use, consumed when the talk is created, never a public link, and bytes bypass the conversation so deck size doesn't affect context length. This is exactly the kind of operational context annotations can't express.

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 flow is front-loaded (what it does, what it returns, how the bytes are sent), followed by the ticket properties and the drop_url fallback. Every sentence carries actionable information; none is padding.

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?

Though there is no output schema, the description documents the return values (upload_url, upload_id) and the full end-to-end contract up to aitho_create_talk. For a one-parameter tool, nothing an agent needs to invoke it correctly is missing.

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 100% for the single filename parameter, including the .pdf/.pptx/.ppt constraint, so the schema already does the work. The description restates the accepted extensions but adds no new syntax or format meaning 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?

States a specific verb (prepare) and resource (deck upload) and precisely what it produces: a short-lived, single-use upload_url and upload_id for one deck file. It clearly distinguishes itself from siblings by naming aitho_create_talk as the downstream consumer and by scoping to exactly one deck file.

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 covers the primary case (user-attached file or file made in the conversation) and the fallback case (agent cannot make HTTP requests → hand the user drop_url). It tells the agent exactly which tool consumes the upload_id and how, leaving nothing to inference.

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