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

With no annotations, the description carries the full burden. It usefully discloses the return shape (ranked matches, confidence, reasons, affiliate_url), which is real added value, but it says nothing about auth requirements, rate limits, whether results are personalized/cached, or how ties are broken.

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?

Purpose is front-loaded in one sentence, followed by a dense but scannable parameter and return summary. The 'Params:' list is terse and every token carries information, though the terse dump style borders on schema restatement.

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 an 8-parameter tool with no annotations and no output schema, the description supplies the key missing pieces: parameter value domains and the returned fields. It falls short only on default values, pagination/limit behavior, and the absence of any sibling-routing guidance.

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 0% and there are no enums in the schema, so the description must compensate — and it largely does, naming all 8 parameters and supplying value vocabularies (side|back|stomach|combination, pain point examples, AUD budgets, 1-10 firmness, bool|1-5 cooling). It omits defaults and the meaning/upper bound of limit, which the schema alone carries.

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 uses a specific verb and resource: 'Match a structured sleep profile to ranked products,' which is far more informative than the bare tool name. It does not, however, explicitly contrast itself with dome_search_products, so the agent must infer that this is profile-driven matching versus keyword search.

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?

Usage is implied by the input shape — supply a sleep profile when you want ranked product matches — but the description never states when to prefer this over dome_search_products or dome_get_retailer_traction. No exclusions or prerequisites are given.

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