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

Annotations already mark readOnlyHint=true, so the safety profile is covered. The description goes well beyond this by disclosing the $0.01 USDC cost, the Base network, the exact payTo address, and the free+paid catalog scope. No contradiction with annotations.

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?

Every clause earns its place: payment cost, search scope, parameter hints, entity coverage, and the global-index caveat. The most operationally critical fact (paid) is front-loaded.

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?

Covers scope, cost, payment address, required and optional parameters, and entity targets. The main gap is that it does not explain how payment must be made (e.g., pre-funding vs. attached transaction) or what the result payload looks like, which is more consequential for a paid tool without an output schema.

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 100%, so the baseline is 3. The description mostly restates q= and limit=1..20, though 'House discovery (board/bid/name + SKUs)' adds useful semantic context for what kinds of queries are meaningful.

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?

States a specific verb+resource: 'search this origin's free + paid catalog by keyword q='. The 'House discovery (board/bid/name + SKUs)' qualifier gives concrete scope, and 'Not a global index' actively distinguishes it from broader search tools.

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?

Gives clear positive context (search local catalog, `q` keyword, optional limit) and an explicit negative boundary ('Not a global index'). It does not name sibling alternatives such as arxiv, cve, or wiki, so the alternatives requirement for a 5 is missing.

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