set_page_background

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

The description discloses that a rectangle is created full-page to act as background, but it does not reveal potential side effects (e.g., overwriting existing backgrounds, layer placement, undo behavior). No annotations exist, so the description carries full burden; it adds basic context but leaves gaps around modification behavior.

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, focused sentence with no extraneous words. It efficiently communicates the core action and mechanism, earning its place without redundancy.

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 no output schema and three optional parameters, the description adequately states the function but lacks context on default page handling, error conditions (e.g., missing color swatch), and whether the operation is additive or destructive. It covers the basics but is not fully comprehensive.

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 100%, with each parameter already described (page index, color swatch requirement, opacity range). The tool description does not add any new meaning or context beyond the schema, so it meets the baseline but does not enhance understanding.

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 action ('Set page background') and the method ('creating a full-page rectangle with specified color'). It uses a specific verb-resource combination, distinguishing it from siblings like 'create_rectangle' which would create an arbitrary rectangle, not a background.

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 implies usage for setting a background color but does not provide explicit guidance on when to use this tool versus alternatives like 'apply_color' or 'create_rectangle'. There are no exclusions or alternatives mentioned, relying on implicit context.

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