x402_search

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

No annotations are present, so the description must convey behavioral context itself. It discloses the read-only search nature and the contents of results, but omits details like pagination, match semantics, filtering behavior (AND/OR), or potential rate limits. The behavioral disclosure is adequate but minimal.

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 two sentences, front-loads the action, and wastes no words. It efficiently conveys both the search capability and the return payload without redundancy.

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?

Without an output schema, the description compensates by listing what results contain. It covers the essential invocation knowledge: resource, filters, and return shape. Minor gaps exist around how filters combine and whether results are paginated, but for a simple search tool this is nearly complete.

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 input schema already documents all three parameters with 100% coverage. The description restates the filter axes (keyword, category, chain) at a high level, which adds a little context about their role, but does not add new meaning beyond the schema. This aligns with the baseline of 3.

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 the verb 'Search' and names the specific resource 'x402 endpoints' for keyword, category, or chain. It also states the return payload (descriptions, prices, URLs), making the tool's function unambiguous and distinct from siblings like x402_list_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 clearly implies the tool is for finding x402 endpoints via filters, but it does not explicitly state when to prefer this over alternatives like x402_list_categories or x402_discover_urls. An agent can infer usage context, but no exclusions or when-not-to-use guidance is provided.

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