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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context the annotations don't: it returns 3-6 curated picks with a one-line reason and links to live searches across named external stores, prices are estimates, and transactions complete off-tool. That is meaningful disclosure for an open-world read tool.

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?

Three tight sentences: capability first, then return shape, then the price/checkout caveat. Nothing is redundant or padded.

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?

With no output schema, the description carries the return-value burden and does it well (count, one-line rationale, store links). It falls short only on the undocumented input parameters and on not differentiating from sibling search tools.

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 only 43%, and the description recapitulates the length enum plus occasion, size and budget without adding format or syntax beyond the schema. It leaves avoid, color and count unexplained in both places, so it does not compensate for the coverage gap.

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 with scope modifiers: 'Find mini, midi or maxi dresses for an occasion, size and budget.' The length-and-style specificity separates it from the generic shop_search sibling, though no sibling is named explicitly.

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?

Implied usage is clear (dress shopping filtered by length/occasion/budget), and it hints at the boundary of the flow by noting checkout happens on the store's site. However it never says when to pick this over shop_search or size_guide, so the agent must infer the routing.

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