set_slide_placeholder_by_idx

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention side effects (e.g., overwriting existing content), error conditions (e.g., invalid index), required permissions, or what the tool returns. The existence of an output schema does not compensate for the lack of description.

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 sentence, which is concise, but it lacks structure and omits critical details. Every sentence should earn its place, but this one is too brief to be fully helpful.

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 moderate complexity (3 required params, no schema descriptions), the description is incomplete. It does not explain the output, error behavior, or any constraints like valid indices. The presence of an output schema is not leveraged. The tool could not be used reliably without additional knowledge.

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?

With 0% schema description coverage, the description must compensate. It only explains 'placeholder_idx' as a layout index, but leaves 'slide_index' (presumably slide position) and 'text' (content to set) largely implicit. The phrase 'set a placeholder' does not clarify that 'text' is the value to set on an existing placeholder, leading to ambiguity.

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 verb 'Set' and the resource 'placeholder on an existing slide', and specifies the method 'by its layout idx', distinguishing it from the sibling 'set_slide_placeholder' which likely uses a different identifier. However, the wording 'set a placeholder' is slightly ambiguous about whether it creates or updates content, given that 'text' is a parameter.

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 is given on when to use this tool vs. alternatives like 'set_slide_placeholder' or 'set_slide_title'. The description does not mention prerequisites, required order of operations, or any conditions under which the tool should be avoided.

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