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

With no annotations, the description carries full behavioral disclosure. It reveals that search is fuzzy, that it resolves to a pool_uid, and adds cost information ('$0.001 per call via x402'), which goes beyond the schema. It does not describe the full return structure, but the core behavior is transparent.

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 concise sentences with no redundant words. The core action is front-loaded, and the cost note is relevant and succinct.

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 description is fairly complete for a simple search tool: it states the purpose, the output type (pool_uid), and cost. It lacks details on return structure, empty results, or error behavior, but this is mitigated by the clear purpose and the absence of 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 0%, so the description must compensate. It does define the 'keyword' parameter as 'protocol name / pool name / asset', which is helpful. However, the 'limit' parameter is not explained, leaving it undocumented beyond the schema's basic type and range.

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 clearly states the action ('Fuzzy search') and resource ('Barker's pool index'), then explains the purpose ('Resolves natural-language pool references to pool_uid for the detail/history tools'). This distinguishes it from sibling tools like barker_pool_detail and barker_pool_history.

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 when to use it: when you have a natural-language pool reference and need to get the pool_uid for detail/history tools. However, it does not explicitly name alternative tools or state when not to use it, but the context is clear enough.

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