ppt_batch_modify_shapes

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

With no annotations, the description carries the burden of behavioral disclosure. It does mention pre-validation of shape IDs and atomic application, which is valuable. However, it omits details on error handling when validation fails, whether changes are in-memory or require saving, and side effects on the presentation. These gaps are significant for a mutation tool.

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 two concise sentences, front-loading the purpose and key behavioral traits. No redundant wording exists. It could be slightly more structured (e.g., listing operation fields), but it is appropriately compact given the content.

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?

This is a complex batch tool with an operations array whose item schema is entirely untyped (additionalProperties true). The description does not explain what an operation object should contain, nor does it clarify prerequisites like an open presentation. While an output schema exists, it cannot compensate for missing usage details about input construction. The description is insufficient for an agent to invoke this tool correctly.

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 explain parameters. It only lists high-level geometry categories (positions, sizes, rotations, z-orders) but does not describe the structure of the operations array items, the meaning of slide_number, or the role of presentation_path (default null). An agent cannot correctly construct the operations array from this description alone.

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 states a specific verb (modify) and resource (multiple shape geometries) with concrete attributes (positions, sizes, rotations, z-orders). It clearly differentiates from single-shape tools like ppt_modify_shape and batch text modification, making the tool's scope unambiguous.

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 phrase 'in a single transaction' implies a batch use case and atomicity benefit, but the description does not explicitly contrast with calling ppt_modify_shape repeatedly or state when a single-shape tool would be preferable. No exclusions or alternative routing are provided, leaving selection partially to inference.

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