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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds valuable behavioral details: it excludes partial replacements unless include_partial, and never lists trials, one-time credits, expiring or non-commercial plans. It also includes a privacy disclosure about how arguments are stored, which goes beyond the annotations. These are meaningful additions beyond the structured hints.

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 first sentence is concise and informative, but the second sentence is a long, boilerplate privacy notice that is tangentially related to the tool's operation. It spans several clauses and distracts from the core purpose. The description is not front-loaded; the key info is in the first sentence, but the excess text makes it less concise.

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?

This is a read-only query tool with 5 optional parameters and no output schema. The description only explains the filtering behavior and the privacy policy, but does not describe the parameters or the expected return format. An agent would need to infer parameter meanings from the schema alone, which is insufficient. The privacy disclosure, while important, is not directly about the tool's usage. Overall, the description is incomplete for a tool with this parameter complexity.

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 the description does not explain any parameters except mentioning 'include_partial' by name. The schema itself has 5 parameters (limit, metric, category, path_type, include_partial) with enums and defaults, but the description adds no semantic meaning to these parameters. For example, it doesn't clarify what 'metric' values mean or how 'category' or 'path_type' are used. This is a critical 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?

The description clearly states the tool returns 'top replacement paths across the catalog' sorted by savings, payback months, or popularity. This is a specific verb (get/leaderboard) and resource (replacement paths). It does not explicitly differentiate from sibling tools like find_alternatives or list_categories, but the leaderboard concept is distinct enough to understand its purpose.

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 this is used when you need a ranked list of replacement paths, but it does not explicitly state when to prefer this over alternatives or mention any exclusions beyond the data filtering. The sibling context suggests other tools for different purposes, but the description itself does not guide the agent on when to use this tool.

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