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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is covered. The description adds that design and utility model patents are supported and maps utility models to patentType U with model 3 or 4, but it does not disclose auth needs, rate limits, result format, or latency characteristics.

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 core capability is front-loaded clearly, but the description is bloated with a long list of trigger phrases and keyword variants that reads partly as keyword stuffing. It is not badly organized, but several sentences do not earn their place as operational guidance.

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 24-parameter tool with full schema descriptions and read-only annotations, the description covers the central behavior, supported patent types, and the special utility-model model mapping. It does not explain return values, but with no output schema and strong parameter documentation, the remaining gap is modest.

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%, so the baseline is 3 even without description-level parameter detail. The description adds useful cross-parameter guidance for utility models, but it conflicts with the patentType schema note that says 'this skill uses D,' creating ambiguity rather than cleanly improving parameter understanding.

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 states a specific verb and resource: 'visual similarity search for design patents using an image URL,' and names the filterable dimensions. It is clear enough to distinguish this from generic image search or product search tools, though it does not explicitly contrast itself with sibling patent/image-search tools.

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?

It gives strong when-to-use guidance through explicit trigger phrases and says to invoke it whenever the need involves searching similar design patents through an image, even without the phrase 'patent image.' It does not name alternatives or provide when-not-to-use exclusions, so it falls short of full routing guidance.

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