ppt_apply_style

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

No annotations are provided, so the description carries the full burden. It explicitly states that text content is not changed, which is a useful behavioral guarantee. However, it does not disclose other potential side effects, such as whether existing styles are overwritten, whether shape geometry is affected, or any permission/rate limitations. The level of transparency is moderate but incomplete.

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 a single, efficient sentence that front-loads the primary purpose and lists all presets. It is easy to scan and does not waste words. However, it could be improved by separating the two modes into distinct sentences for clarity, but the current structure is acceptable.

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 complexity (15 parameters, 0% schema coverage, no annotations, but an output schema exists), the description is under-specified. It does not explain the mutual exclusivity or combination rules between preset and manual style parameters, which parameters are needed for each mode, or how shape_ids and shape_id differ. The agent would likely struggle to invoke this correctly without additional context.

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?

The schema has 0% description coverage, so the description must compensate by explaining the parameters. It only introduces two modes (preset and source-shape transfer) via the preset and source_shape_id concepts, but does not explain the roles of fill_color, font_color, line_color, bold, italic, shape_ids, or the source_slide_number/presentation_path parameters. An agent has little guidance on how to set these fields correctly.

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 tool's purpose: applying predefined style presets or transferring fill/border/font styles from a source shape, with an explicit constraint that text content is unchanged. It lists all preset names, making the action concrete and distinguishing it from sibling tools like ppt_modify_shape which handle manual property changes.

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 styling operations (presets or copying styles) but does not explicitly state when to use this tool versus alternatives. It does not mention conditions like 'when you need consistent design' or contrast with ppt_modify_shape or ppt_batch_modify_shapes. The agent must infer the appropriate context from the description alone.

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