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

With no annotations, the description carries the full behavioral burden and does so well: batch cap, per-call pricing, an authentication restriction, and the ambiguity/unknown-name failure mode that returns candidates instead of an entry. Return payload fields are also enumerated.

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?

Front-loaded with the core action, then output shape, then pricing and auth caveats — every clause earns its place. Slightly dense phrasing in the second sentence, but no filler.

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 one-parameter tool with an output schema, the description covers batching, cost, auth restrictions, and return semantics adequately. Missing only edge details like idempotency or rate limits beyond the flat per-call price.

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 single schema parameter has 100% description coverage (array of strings or { name, namespace?, venue? }, 1-25 items), so the schema already does the heavy lifting. The description largely restates that item format and defers semantics to 'the same hints as lexicon_resolve', adding only marginal meaning.

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 (resolving up to 25 names against the ChainHelix Agentic Lexicon) and its output shape (entry fields or candidates). The phrase 'in one call' plus the cross-reference to lexicon_resolve makes the bulk-vs-single distinction clear without opening either schema.

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 context for use: batch up to 25 names, cost of 50 cents per call, and the caveat that a ChainHelix API key does not cover it. It does not explicitly say to prefer lexicon_resolve for a single name, leaving that inference to the agent.

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