tolly_routed_search

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

With no annotations provided, the description carries the disclosure burden well: it states the search is free, explains the all-in price includes a disclosed 10% fee with a $0.001 minimum, notes the direct-purchase alternative, and warns that seller-provided titles/descriptions are untrusted. It does not mention pagination, ordering, or rate limits.

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 front-loaded with the core action and scope, then efficiently lists return fields, purchase alternatives, and the trust warning. Every sentence contributes useful information without repetition.

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?

Because there is no output schema, the description appropriately enumerates the returned fields and explains the fee composition. It also covers the direct-purchase alternative and untrusted seller text. Minor gaps remain around pagination and result ordering, but these are not critical for correct invocation.

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 coverage is 67%, and the description importantly defines 'all-in price' as seller price plus TOLLY's 10% fee with a minimum, which clarifies maxPriceUsd beyond the schema. However, it adds no detail about the limit parameter or query matching rules, leaving some parameter semantics to 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 gives a specific verb and resource: search other sellers' x402 services that TOLLY routes. It also clarifies the scope ('free', routed services) and lists returned fields. It does not explicitly contrast with sibling tools such as tolly_list_services, so it falls short of full sibling differentiation.

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 clearly states the next action: buy with tolly_routed_buy, or purchase directly from the seller URL instead. It also notes that search itself is free. It does not explain when to use this versus tolly_list_services or other search siblings.

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