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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is added context — and it delivers: results carry a recorded check status, and missing/unreachable/needs-a-key entries are convertible into requests rather than dead ends. The next-page behavior ('data.next says what to do') is genuinely useful behavioral disclosure absent from 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?

Three sentences, front-loaded with the resource and its exclusions before the recovery paths. The final sentence is long and packs three tool names plus a JSON field, but every clause carries routing information rather than 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?

No output schema exists, and the description compensates by explaining the shape of the empty-result response (data.next with ask_for_it / open_pot / post_bounty). Combined with the recorded-status note, an agent knows enough to call it and act on the result; only the pagination/cursor and limit behavior remain entirely on the 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 coverage is 80%, so the baseline is 3; the description pushes above it by explaining the query-matching semantics and by narrating the status conditions ('needs a key, does not answer, or was not found') that map onto the otherwise undescribed status enum. It still says nothing about url, limit, or cursor beyond the schema text.

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 and resource ('Search remote MCP endpoints from external public registries') plus a scope qualifier ('including the status Licium recorded when checking them'). It also explicitly negates the nearest confusion ('These are not Licium bounty agents'), so an agent can separate this from bounties_list and capabilities_list without opening schemas.

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 concrete fallback routing: when a query matches nothing, follow data.next to request_source, the open bounty (pledge_url), or bounty_post. It does not state the primary when-to-use condition versus capabilities_list/exchanges_search, so the guidance is strong on dead ends but silent on the main alternative selection.

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