post_process_powerpoint

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

With no annotations provided, the description carries full burden. It mentions the tool 'enables text wrapping and shrink text on overflow' which describes behavior, but lacks details on permissions needed, whether the original file is modified or a new file is created, error conditions, or rate limits. For a mutation tool with zero annotation coverage, this is insufficient.

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 a purpose statement, parameter explanations, and return value note. Each sentence adds value, though the parameter explanations could be slightly more concise. It's appropriately sized for a 4-parameter tool.

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 the tool's moderate complexity (4 parameters, mutation operation) and no annotations, the description does well by explaining all parameters and noting the return is a success message. With an output schema present, it doesn't need to detail return values. However, it could better address behavioral aspects like file handling or error cases.

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%, so the description must compensate. It provides meaningful context for all 4 parameters: input_file specifies format (.pptx), output_file explains auto-generation, text_threshold clarifies it overrides .env settings, and enable_autofit notes its default. This adds substantial value beyond the bare 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?

The description clearly states the specific action ('Apply post-processing'), target resource ('PowerPoint presentation'), and purpose ('to optimize text boxes'). It distinguishes this tool from siblings like get_slide_info or translate_powerpoint by focusing on text box optimization rather than retrieval or translation.

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 text box optimization when text exceeds a threshold, but doesn't explicitly state when to use this tool versus alternatives like translate_powerpoint or when not to use it (e.g., for non-text elements). No prerequisites or exclusions are mentioned.

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