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

Annotations already declare readOnlyHint and idempotentHint, so the description's mention of 'Read-only, free' aligns but adds only marginal value. It reinforces the safe nature but does not disclose any additional behavioral traits beyond what annotations provide. The description does not contradict annotations.

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 concise (three short sentences) and front-loaded with the core purpose. Each sentence adds value: identifying presets, distinguishing categories, stating read-only nature, explaining filtering, and paging. No fluff or repetition.

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 5 parameters and no output schema, the description covers filtering, scoping, and paging. It does not describe the return format, but the omission is acceptable given the annotations (read-only) and the clear input schema. The context is sufficient for an agent to select and invoke the tool correctly among many sibling list tools.

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%, and the description adds meaningful context: mutual exclusivity of only_official/only_workspace, default values for limit and offset, and the scoping behavior of brand_id. This goes beyond the schema's own descriptions, which already include details. The description helps the agent understand parameter interactions.

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 lists saved visual style presets, defines workspace vs official categories, and explains filtering options. The verb 'list' combined with resource 'visual_style_presets' with specific scope details makes the purpose unmistakable. It also distinguishes the tool from siblings by mentioning the Heista catalog and org ownership.

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 explains how to filter using only_workspace/only_official (mutually exclusive) and how to page with limit+offset. It provides clear context on when each filter applies, though it does not explicitly mention when to prefer this tool over alternatives like get_visual_style_preset or other list tools. Still, the guidance on filter usage is explicit and actionable.

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