document.set_slide_background

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

With no annotations, the description carries the full burden and says almost nothing: not whether the background replaces or layers over an existing one, not whether a theme/master background is overridden, and not whether the operation is undoable. Only the fact that a mutation happens is conveyed.

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?

A single front-loaded sentence with no waste. It is efficient, but that efficiency comes at the cost of omitted detail rather than through disciplined editing.

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 an unannotated, output-schema-less mutation tool with an undocumented required target concept, the description is too thin. An agent cannot tell from it whether 'index' is required in practice to identify the slide or what happens when it is omitted.

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 coverage is 50%: 'color' already has an example in the schema, so 'hex color' adds little, and the 'index' parameter is unexplained in both the schema and the description. The description does not resolve the key ambiguity of how the target slide is selected.

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?

States a specific verb ('Set') and resource ('a slide's background') plus the value type (hex color). It is distinguishable from siblings like set_slide_title or set_slide_transition, though it doesn't clarify which slide is targeted.

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 indication of when to use this versus other slide-styling setters, no prerequisites, and no statement about whether the change is per-slide or deck-wide. Usage is only inferable from the name.

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