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

With no annotations, the description carries the full burden and does disclose real behavior: no API key required, the free set is limited to three house styles, and it returns download URLs for matches or the full word list otherwise. It does not cover failure modes, rate limits, or cost implications beyond 'free', which keeps it from 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?

Four short, front-loaded sentences with no filler. The core action leads, the key constraint follows, and the return behavior closes it out; every sentence carries information an agent needs.

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?

There is no output schema, and the description compensates by describing the return value (download URLs, or the full word list on no match). With no annotations, it adequately covers key/safety context, though it leaves error and no-match handling only partially specified.

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 50%: the concept param is documented in the schema, while style has only an enum with no description. The description reinforces the style constraint by naming the same three styles and explaining they are the free set's limit, which adds value, but it adds no syntax or matching semantics for concept.

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?

States a specific verb+resource with scope: "Find a free, ready-made transparent PNG icon from the Claycut catalogue." The word "free" and "catalogue" implicitly distinguish it from the sibling tools (find_my_icon, generate_app_icon, edit_app_icon), but none of those siblings is named, so the differentiation is left to inference.

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?

Gives an explicit selection condition: use it when the project's CLAYCUT.md style is clay/editorial/plush, or the user has no key; otherwise it won't match the project. That is a clear when/when-not rule, though no alternative tool is named for the cases where this tool is the wrong choice.

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