set_slide_title

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

The description only says 'set', implying a mutation, but does not disclose side effects (e.g., overwrites existing title), behavior when no title placeholder exists, or whether the operation is reversible. No annotations are provided, so the description should bear the full burden but fails.

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 lacks structure. It does not front-load critical information (e.g., mutation behavior) and provides only a bare statement.

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?

For a tool with two parameters and no annotations, the description is incomplete. It omits parameter explanations, behavior details, and return value despite an output schema existing. The sibling tools like set_slide_placeholder suggest broader functionality, but this description does not cover the specific 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?

With 0% schema description coverage, the description adds no meaning to the parameters (slide_index and text). The schema provides titles but no explanations; the description does not clarify what slide_index refers to (e.g., what indexing scheme) or any text formatting constraints.

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 sets the title placeholder of a slide, distinguishing it from generic placeholder setters like set_slide_placeholder. However, it does not explicitly differentiate from set_slide_placeholder_by_idx, which might also target the title placeholder by index.

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 versus alternatives (e.g., set_slide_placeholder, read_slide). The description lacks prerequisites or context for use, such as requiring a presentation to be open.

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