create_style

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

Without annotations, the description partially discloses behavior: name becomes styleId after removing spaces. However, it omits key details like whether existing styles with the same derived styleId are overwritten, error handling for invalid names, or required document state.

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 relatively concise with a clear parameter list using bullet points. The first sentence clearly states the action. Could be slightly more front-loaded with the styleId derivation.

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 simplicity and existence of output schema, the description covers core functionality. However, it lacks information on return value (styleId?), conflicts with existing styles, and validation constraints, which would be helpful for a creation tool.

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 0%, but the description adds significant meaning: explains that name is used as styleId, lists allowed values for style_type, and clarifies the role of based_on and next_style. Could be improved by explicitly listing style_type options.

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 'Create a new style in the document,' which is a specific verb+resource combination. Among siblings like copy_style, update_style, get_style, delete_style, and apply_style_to_range, this tool's purpose is unambiguous.

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 on when to use this tool versus alternatives like copy_style or update_style. No prerequisites (e.g., style name uniqueness) or conditions for creation are mentioned.

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