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

The read-only, idempotent, and non-destructive traits are already supplied by annotations, so the description only needs to add extra behavioral context. It does so with the clause 'using the same order-based product profit math as the dashboard,' which clarifies the exact profit methodology and promises dashboard-consistent figures. There is no contradiction with the 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?

The description is a single sentence with the action and result front-loaded: 'Get the top N products ranked...'. The final clause about dashboard math is the only elaboration and it earns its place by specifying methodology. There is no filler, repetition, or restatement of the title.

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 a read-only ranked-list tool with a fully documented input schema, an output schema, and annotations covering safety, the description covers the remaining essentials: what is returned, the ranking dimensions, and the date range. Operational details such as the 50-product cap, timezone resolution, and 'highest first' ordering live in the schema, so nothing critical is missing.

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%, with start_date, end_date, limit, and rank_by all individually documented, including format, bounds, defaults, and enum values. The description only restates those concepts at a high level ('ranked by revenue, profit, margin, or units sold', 'over a date range') and does not add new parameter-level meaning. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Get the top N products ranked by revenue, profit, margin, or units sold over a date range.' The 'top N' phrasing separates it from the sibling get_bottom_products, and the ranking-metric list makes clear this is a ranked list rather than a detail lookup like get_product_detail.

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 when a ranked list is wanted, but it never states when to prefer this tool over alternatives such as get_bottom_products or get_product_detail, nor does it give any when-not-to-use conditions. An agent has to infer applicability from the name and sibling list rather than from explicit routing guidance.

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