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

Annotations already declare the non-read-only, non-destructive, non-idempotent profile, and the description usefully adds that formatting is preserved and which language families are supported. It does not disclose the mutation's observable behavior — whether it creates a new job/deck, how the result is later retrieved, or what happens to the source deck.

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 compact sentences, front-loaded with the operation, then the capability, then the input modes. No filler, though the language list slightly duplicates the target_language enum the schema already provides.

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?

For a 10-parameter mutation tool with no output schema, the description leaves the return behavior (job handle, preview, polling) unexplained, which the agent needs given include_preview and the job-based workflow. It is adequate for selecting the tool but not for predicting the outcome.

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%, so the schema already documents all 10 parameters including defaults and the 'preferred' note on job_id. The description only re-enumerates the three source options and the language coverage, adding a cross-tool pointer (job_id comes from create_slide/create_deck) but little 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 and resource (translate a .pptx deck) plus a distinguishing qualifier (preserving all formatting), which lets an agent separate it from the create/edit siblings. It stops short of naming any sibling tool it should be used instead of, so it is clear but not fully differentiated.

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 sentence naming the three source modes (job_id, pptx_url, pptx_base64) tells the agent which inputs are acceptable, but gives no when/when-not guidance relative to siblings like edit_deck or create_slide. Usage is implied by the input hints rather than stated as a decision rule.

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