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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely useful behavior beyond them: the 20-item cap on blank queries and the warning that listings are self-reported claims rather than verified facts. It stops short of describing pagination or exact return fields.

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 core purpose and blank-query rule are front-loaded, but the final sentence about the console is lengthy and somewhat tangential to search behavior. It does earn partial keep as directory context, yet trimming would improve focus.

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 single-parameter read tool with no output schema, the description covers scope, result cap, and data-trust caveats adequately. It omits any indication of result shape or ordering, but nothing essential to correct invocation is missing.

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 100%, so the parameter is already documented, but the description adds real semantics the schema lacks: an empty query returns the whole directory (up to 20). That syntax-to-outcome mapping meaningfully exceeds the schema baseline.

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 (Search) plus the exact resource (Voicescape on-chain agent directory) and the axes of search (username or purpose text). The blank-query behavior further pins down scope so an agent can distinguish it from unrelated list/search siblings.

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 operating context: blank query lists the entire directory, results are capped at 20, and the caller should verify before paying. It does not name a sibling alternative or a hard when-not condition, which keeps it short of a 5.

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