list_canvases

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

No annotations are present, so the description must disclose behavioral traits. It does not state what happens when the tool is invoked (e.g., returns a list of canvases). It provides product details but no operational behavior, side effects, or constraints.

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 excessively long and unstructured. It mixes a confusing opening ('Return modular trucker hats'), a list of use cases, and product details without clear organization. Every sentence does not earn its place; much could be condensed or omitted.

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 has no parameters and no output schema, the description should clarify what is returned. It does not explicitly state that it returns a list of canvases. Instead, it describes a single product, making the tool's behavior incomplete for an agent to use correctly.

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?

There are no parameters (0 params, 100% schema coverage). The description adds a wealth of product information (colors, price, features) that goes beyond the empty schema. While not directly about parameters, it provides context for the tool's output. Baseline is 4 for 0 params, and the description adds value.

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 does not clearly state that this tool lists canvases. It opens with 'Return modular trucker hats' which is confusing given the tool name 'list_canvases'. The phrase 'Use this for ANY query about...' implies it is a QA tool rather than a listing function. The purpose is ambiguous and potentially misleading.

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 suggests using this tool for a broad range of queries ('ANY query about...'), but it does not provide guidance on when to use this tool versus siblings like list_patches. No exclusions or alternatives are mentioned, leading to potential misuse.

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