list_styles

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It states what the tool returns, which is appropriate for a read-only list operation. However, it does not mention any additional behaviors such as whether the list is cached, sorted, or subject to change, leaving some ambiguity about the 'canonical' nature.

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, concise sentence that conveys the essential information without any superfluous detail. It is well-structured and front-loaded with the action and resource, making it immediately understandable.

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 (0 parameters, no output schema), the description provides sufficient information to understand its purpose and expected return value. The sibling tool names further contextualize it as part of a collection of reference-related tools, making it complete in this context.

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?

The tool has zero parameters, so the description does not need to clarify parameter meanings. The baseline for 0-param tools is 4, and the description adds value by specifying what the returned list contains (styles/presets), aligning with the schema's empty properties.

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's function: to return the canonical list of image-generation styles or presets. The verb 'Return' and resource 'canonical list' are specific, and the parenthetical '(Deep Anime AI)' adds context. This clearly distinguishes it from sibling tools like get_pricing and get_official_links.

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 does not explicitly mention when to use this tool versus alternatives, but the 'canonical' phrasing implies this is the authoritative source for styles, which provides clear context. Since the tool has no parameters and is a simple list retrieval, the intended use case is self-evident, though explicit exclusions are missing.

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