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

No annotations are provided, and the description only hints at output joining data but does not disclose whether the operation is read-only, destructive, or any side effects. The agent lacks critical behavioral cues.

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 a single 11-word sentence, which is concise but lacks sufficient detail. It front-loads the purpose but omits important context. Appropriate length given minimalism, but space is not well-used.

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 3 parameters with no documentation, no annotations, and sibling tools requiring differentiation, the description is incomplete. The presence of an output schema helps, but the tool is under-documented for reliable agent use.

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 0% with no parameter descriptions. The description only mentions 'category' implicitly, ignoring 'limit' and 'in_stock_only'. It fails to compensate for the lack of schema documentation.

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?

Description clearly states it finds offerings matching a category, with join to merchant and capabilities. The verb-resource combination is specific and distinguishes it from siblings like find_best_merchant or get_merchant_view, though no explicit differentiation is provided.

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 implies usage for category-based search for offerings, but provides no guidance on when not to use this tool, prerequisites, or alternatives among siblings. Context signals are not leveraged.

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