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

Goes well beyond the annotations by disclosing the restricted category (Clothing, Shoes and Accessories only), eBay's look-alike ordering, the fallback behavior when the image is not one item (`matches` empty and a say line asks what the item is), and the effect of q on filtering results. These are substantive behavioral traits not covered by the readOnly/idempotent/destructive annotations.

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?

Front-loaded and mostly efficient: purpose, usage, required image link, return behavior, fallback case, and q guidance. The opening brand line 'Wardrobe Connect.' is redundant with the namespace/title, but the rest of the sentences earn their place.

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 no output schema, the description supplies enough return-shape context (`matches` empty, say line asks what the item is) and category/order details. Annotations cover the safety profile and the schema covers all parameters, so an agent has what it needs to invoke the tool 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 description coverage is 100%, so the baseline is 3. The description adds meaningful guidance for q, calling it 'strongly recommended' and explaining that results must match it to remove wrong-kind look-alikes, which strengthens the schema's own q description.

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 and resource: 'Find clothes that look like a picture' and returns visually similar eBay listings. The image-based nature is clear from the description and tool name, but it does not explicitly name or contrast with the sibling wardrobeconnect_find_clothes tool.

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 clear when-to-use context: 'Use when the user shares or points at a picture of an outfit or item (a Pinterest pin, a saved post, a photo).' It also advises adding a short q description, but does not state when-not to use this tool or name an alternative text-search sibling.

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