translate_powerpoint

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions 'AWS Bedrock model' and 'polishing' but doesn't disclose rate limits, authentication requirements, file size constraints, whether the original file is modified, or error handling. The return statement is vague ('Success message with translation details').

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 description is well-structured with clear sections (purpose, Args, Returns) and front-loaded the core function. However, the 'Returns' statement is somewhat vague, and some sentences could be more precise (e.g., 'auto-generated if not provided' is efficient).

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 5 parameters with 0% schema coverage, no annotations, and an output schema present, the description does a decent job but has gaps. It explains parameters but lacks behavioral context (e.g., side effects, limitations). The output schema existence means return values don't need explanation, but more operational guidance would help.

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%, but the description compensates well by explaining all 5 parameters in the Args section. It clarifies 'output_file' auto-generation, provides language code examples, and explains 'enable_polishing' purpose. However, it doesn't detail 'model_id' options or 'input_file' format beyond '.pptx'.

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?

The description clearly states the specific action ('Translate a PowerPoint presentation') and resource ('PowerPoint presentation'), distinguishing it from siblings like 'translate_specific_slides' (partial translation) and 'post_process_powerpoint' (different operation). The verb 'translate' is precise and the scope is well-defined.

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 description implies usage for full presentation translation but doesn't explicitly state when to use this vs. 'translate_specific_slides' (partial slides) or 'post_process_powerpoint' (non-translation processing). No guidance on prerequisites like file format compatibility or when not to use this tool is provided.

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