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

No annotations exist, so the description carries the full burden. It does not state that the operation is read-only/no-side-effect, does not describe the return structure beyond 'endpoints with examples,' and does not say whether the card is static or reflects live network state. The mention of 'ready-to-run call examples' is the only real behavioral disclosure.

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?

A single compact sentence with no filler, and the payload contents are front-loaded after the colon. It could be tighter by replacing the 'self-describing' adjective with a plain statement of what is returned, but nothing is wasted.

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 zero-parameter discovery tool with no output schema, the description should clarify the shape of the returned card and how an agent should use it to pick a sibling. It hints at the contents and call examples but leaves the response structure and intended follow-up flow implicit, which is a meaningful gap given there is no output schema to fall back on.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no inputs are needed.

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 says the tool returns a 'network card' containing all ETH-LEGION endpoints and enumerates four of them (inference, score certificate, beacon, tribute deposit), which gives a partial sense of the payload. However, 'network card' is undefined jargon and there is no explicit verb-plus-resource statement like 'list available endpoints' — the agent must infer that this is a discovery/index tool rather than an action.

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?

No when-to-use or when-not-to-use guidance is given, and none of the siblings (run_inference, deposit_asset, get_mission, etc.) are referenced as alternatives. The agent can guess it is a discovery entry point, but the description never says 'call this first' or 'use this to find the right sibling endpoint,' which is the key routing information for a tool like this.

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