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

Annotations already declare that this is a safe, idempotent, read-only, closed-world operation. Beyond that, the description discloses the returned fields and that the list covers all covered proof-of-stake networks. It does not mention ordering, pagination, or freshness, but those are minor for a zero-parameter discovery endpoint.

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 description is two tightly written sentences with no filler. The purpose and returned fields are front-loaded, and the usage guidance follows immediately.

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, read-only listing tool without an output schema, the description covers what it does, what it returns, and when to call it. Nothing critical an agent needs 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?

This tool has zero input parameters, so there are no input parameter semantics to explain. The description usefully clarifies that the returned slug is the "network" argument expected by other tools, adding context about how the output feeds sibling calls.

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 states a specific resource and scope: every proof-of-stake network BitBasic covers. It also enumerates the useful fields returned, including the slug, token, kind, validator term, and dashboard, so the agent can distinguish this discovery tool from siblings that operate on validators or reports.

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?

It gives clear usage guidance: start here when the network slug is unknown. It explains that the returned slug is the "network" argument used by the other tools. However, it does not explicitly state when not to use it or name specific alternative tools for cases where the slug is already known.

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