slides_set_shape_fill

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does add the important constraint that the color must be a hex color (e.g., '#FF0000'), which is useful. However, it does not disclose any side effects, permissions, or reversibility, which for a mutation tool with no annotations leaves some ambiguity, though the operation is straightforward.

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 that is front-loaded with the action and resource, and the parenthetical note adds the critical color format example without unnecessary detail. Every word earns its place.

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?

This is a simple mutation tool with an output schema, so the description does not need to explain return values. However, given the lack of annotations and the need to fully define parameter semantics, the description could provide more context about what 'background fill' refers to (e.g., whether it affects the shape outline or text) or mention that it overrides the existing fill color. It is adequate but has clear gaps.

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 for parameter meanings. It provides the format for 'color' (hex) but gives no additional meaning for 'presentation_id' or 'shape_id', which are not described in the schema either. Thus, two of the three parameters remain undocumented beyond their names.

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 uses the specific verb 'Set' with the resource 'shape' and attribute 'background fill color', which clearly and unambiguously states what the tool does. It also distinguishes itself from the sibling tool 'slides_set_background' by specifying the fill color of a shape, not the slide 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 when a shape's fill color needs to be changed, but it does not explicitly state when to use this tool versus alternatives like 'slides_set_background' or how it relates to other shape formatting tools. No exclusions or prerequisites are mentioned, so it relies on the user to infer appropriate use from the purpose.

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