list_cleared_services

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys a read-only catalog load and distinguishes itself from single-origin checks, but it does not disclose pagination, result shape, or any notable constraints, which matters for a tool with no output schema.

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, with the core purpose first and the sibling guidance second. Every phrase earns its place; there is no padding or schema duplication.

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 2-parameter, optional-parameter list tool, the description plus schema provides enough to invoke it: what it lists, the available filters, and when to use it versus alternatives. Missing pagination/output details keep it from a 5, but nothing essential blocks a correct call.

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?

The schema already documents both optional parameters with descriptive text and allowed values, so schema coverage is 100%. The description only restates the category filter and adds no new meaning beyond the schema's parameter descriptions.

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 leads with a specific verb ('List') and resource ('verified services on ClearedIndex'), and explicitly marks category filtering as optional. It also contrasts itself with cleared_check/lookup_merchant, so the agent can tell catalog listing apart from single-origin lookups.

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?

It gives an explicit routing rule: prefer cleared_check or lookup_merchant for single-origin sandwich steps, and use this tool to 'load the catalog.' That is a clear when-not-to-use instruction plus alternative selection, leaving little ambiguity.

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