powerpoint_native_batch

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is carried elsewhere. The description adds concrete behavioral context the annotations do not: it drives 'real Microsoft PowerPoint', works on active or closed presentations, and uses points as native coordinates. It does not discuss persistence (is a save op required?), failure/rollback, or rate/complexity limits for a destructive batch.

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?

Front-loaded with the core verb and resource, and the remaining content is compact. The long capabilities enumeration is dense but arguably earns its place by signaling the batch's breadth; it could be trimmed but is not padded with filler.

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?

With no output schema and a destructive, non-idempotent batch, the description should clarify persistence requirements, ordering semantics, and failure behavior. It states 'ordered batch' but says nothing about how partial failures are handled or whether a 'save' op is mandatory, leaving real gaps for a 40-op tool.

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 reported at 0% for a 3-parameter, deeply nested tool, so the description must compensate and partially does: '!!' prefix for Morph matching, list_shapes as the source of shape references, and 'native coordinates are points' clarify units the schema leaves implicit. However, the vast majority of operation fields (animation timing, export quality, transitions, etc.) receive no explanation, leaving the burden on the schema 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 opening sentence names a specific verb (execute) and resource (ordered batch through real Microsoft PowerPoint), and the 'batch' framing distinguishes it from the single-purpose powerpoint_create_* / powerpoint_replace_text siblings. The feature enumeration that follows broadens scope but doesn't dilute the core identity. It stops short of explicitly naming which sibling covers a given task.

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?

One concrete instruction ('Use list_shapes before targeting shapes') is genuinely useful, but there is no when-to-use/when-not guidance relative to overlapping siblings like powerpoint_render_presentation, powerpoint_replace_text, or powerpoint_inspect_presentation, all of which are subsumed by operations here. The agent must infer when the batch tool beats the dedicated tools.

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