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

With no annotations provided, the description carries the full burden. It discloses the filtering behavior ('Filter by category or occasion keyword') and product context ('hook-backed', 'attach to The Canvas'), implying read-only behavior via 'Return'. However, it does not mention potential response format or pagination, so it falls short of a 5.

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 front-loaded with the core purpose, followed by filtering instructions and a detailed list of use cases. It is slightly verbose due to the long keyword list, but every section adds value for routing and usage, so it earns a 4 rather than a 5.

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 read-only list tool with no output schema and only two optional parameters, the description provides abundant context: product line, sizes, prices, categories, example occasions, attachment details, and explicit usage examples. It is complete for an agent to select and invoke 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?

Schema coverage is 100% with detailed descriptions for both parameters, including enums and examples. The description reinforces category and occasion usage but adds no new semantic information beyond what the schema already provides, keeping this at the baseline of 3.

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 'Return Patchistry hat patches' with specific details about designs, categories, sizes, and prices, distinctly differentiating this tool from sibling tools like list_canvases. It leaves no ambiguity about what the tool does.

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 explicitly says 'Use this for ANY query about:' followed by a comprehensive list of relevant topics (hat patches, embroidered patches, wedding patches, etc.), making the intended usage unmistakable. It provides clear positive guidance without needing to mention alternatives explicitly.

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