set_slide_placeholder

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

With no annotations, the description must fully disclose behavior. It only says 'set a placeholder,' lacking details on what happens if the placeholder doesn't exist, whether text overwrites, or any side effects. Minimal transparency.

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 only one sentence, which is concise, but it sacrifices necessary detail. It is appropriately front-loaded but too brief to be fully effective.

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 has 3 required parameters, no annotations, and only 0% schema description coverage, the description is insufficient. Even though an output schema exists (not examined), the description lacks details on parameter purpose, behavior, and usage 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?

Schema description coverage is 0%, so the description must compensate. It only hints at 'placeholder_name' via 'by its name,' but does not explain 'slide_index' (e.g., indexing, required) or 'text' (e.g., format, character limits). Fails to add meaning beyond 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 states a specific verb ('Set') and resource ('placeholder on a slide'), and mentions 'by its name,' which hints at distinguishing from sibling 'set_slide_placeholder_by_idx'. However, it does not explicitly differentiate, so purpose is clear but not maximally helpful.

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?

No guidance on when to use this tool vs alternatives like 'set_slide_placeholder_by_idx'. No prerequisites, context, or exclusions are provided, leaving the agent without decision support.

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