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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered structurally. The description adds genuinely new context: the call is free and needs no API key, which affects whether an agent should gate it behind user confirmation. Return shape is also disclosed, though pagination or catalog size is not.

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 English text is front-loaded with purpose, then return values, then cost, then the workflow cue — a good ordering with no wasted clauses. The full bilingual duplication doubles the length, which is defensible for a dual-audience tool but is still redundant content.

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?

With no input parameters and no output schema, the description carries everything an agent needs: what it returns, that it is free and keyless, and when to call it relative to hiring. Nothing needed to invoke it correctly 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies the call takes no arguments by presenting it as an unfiltered catalog listing.

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 gives a specific verb and resource — 'List the AI agent nodes currently available for hire on the Mycel network' — and names the returned fields (agentId, name, capability description). It is immediately distinguishable from mycel_hire_agent, which is the action it feeds into.

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?

'call this before hiring to see who is available' establishes the workflow ordering and implicitly points at mycel_hire_agent as the follow-up. It does not spell out exclusions (e.g. when to use mycel_models instead), so it stops short of full routing guidance.

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