top_merchants

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

No annotations are provided, so the description carries full burden. It only states the core function without disclosing behavioral details such as aggregation logic, sorting order, or response format. The description adds no context beyond the bare purpose.

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, clear sentence with no redundant words. It immediately states the tool's purpose without extra fluff.

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?

The tool has no output schema and no annotations, yet the description does not describe the return structure or any behavioral specifics. While the schema covers parameters, the agent lacks information about what the response contains, such as merchant names and spending totals. This makes the description insufficient for full contextual understanding.

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?

All four parameters are fully described in the schema (100% coverage), so the description does not need to add parameter semantics. The phrase 'date range' loosely corresponds to dateFrom and dateTo, but no additional meaning is added beyond the schema.

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 the verb 'find' and specifies the resource 'merchants/payees' with a clear scope 'highest spending in a date range'. This differentiates it from sibling tools like spending_by_category which focuses on categories.

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 user needs top merchants by spending, but it does not explicitly mention alternatives or exclusion criteria. No comparison with sibling tools is provided, leaving the agent to infer the correct tool selection.

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