ppt_compare_slides

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

No annotations are provided, so the description must disclose behavioral traits. It states that the tool compares and matches shapes with confidence scores, but it does not disclose side effects (e.g., read-only nature), performance implications, or how it handles mismatched shapes. The absence of any mutation hint is not sufficient; explicit statements about non-destructiveness are expected for a tool with no annotation coverage.

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 key behaviors. It avoids redundancy and is appropriately sized for the tool's complexity, though it could briefly touch on parameters.

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?

The output schema exists, so return format is covered. However, the tool exposes five parameters with zero documentation, and the description provides no behavioral or usage context beyond the core purpose. For a comparison tool with matching logic and flags, this is incomplete and leaves the agent guessing on parameter semantics and invocation details.

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 by explaining parameter meanings. It makes no mention of render_diff, match_shapes_flag, or presentation_path, leaving the agent to infer from the schema alone, which provides no descriptions. This is a significant gap for a tool with five parameters.

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 compares geometric, typographic, and semantic layout properties between two slides and matches shapes with confidence scores. This provides a specific verb ('compare') and resource ('two slides') and differentiates from siblings like ppt_inspect_slide or ppt_visual_diff by its focus on layout properties and shape matching.

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 does not mention when to use this tool versus alternatives such as ppt_visual_diff or ppt_inspect_slide. There is no guidance on conditions that would favor this tool, exclusion criteria, or prerequisites. The usage is implied by the purpose but not explicitly stated.

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