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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond the annotations: the return carries prices with their verification date and source. It does not mention the default exclusion of unverified offerings or the default sort/limit behavior, which are behavioral facts an agent should know.

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?

Two sentences, both front-loaded: the ranking action and scope come first, the return content second. No filler, no restatement of the title, and every clause carries information.

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 usefully states that results include prices plus verification date and source, which fills part of the return-value gap. Combined with a 100%-covered schema and rich annotations, an agent has nearly everything needed, though the weighting/sort defaults and the unverified-exclusion default are left entirely to the schema for a fairly complex 7-parameter, nested-object tool.

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 every parameter (sort enum, limit, filters, weights, maxPrice, include_unverified) is already documented in the schema, including defaults and ranges. The description only gestures at 'optional requirements and a maximum price' and the three ranking dimensions, adding framing but no new semantic detail. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource ('Rank the offerings in one market') plus the ranking dimensions (price, quality, speed) and the optional narrowing inputs. It is immediately clear what the tool produces, but it never contrasts itself with the sibling 'compare_offerings', which an agent could easily confuse with ranking a whole market.

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 only implied: the phrase 'in one market' and 'optional requirements and a maximum price' signals the shape of a valid call but never states when to reach for this tool over compare_offerings or get_offering. No exclusions, prerequisites, or alternative-routing guidance are given.

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