get_network_status

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

With zero annotations the description carries the full behavioral burden, and it discloses almost nothing beyond 'current status' - not what fields are returned, whether the call hits a live node or a cache, or any rate/failure characteristics. 'Current' implies freshness but is unquantified.

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 core sentence is front-loaded and precise, but the trailing tip is a promotional cross-reference that does no work toward invoking this tool correctly. Two sentences is the right size; one of them is essentially 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 annotations and no output schema, so the description is the only source of information about the return value, and it says nothing about what a 'status' payload contains. An agent can call it, but cannot predict what it will get back or how to use the result.

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 no parameters, so there is nothing for the description to disambiguate; baseline is 4. The empty schema confirms no arguments are needed to invoke it.

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?

Names a specific verb and resource ('Get the current status of the Stacks network'), so the agent knows this is a cheap read of network-level state. It does not, however, distinguish itself from the many adjacent state-read siblings (get_mempool_info, get_pox_info, nonce_health, pillar_status, legion_status), so the agent must infer that 'network' means chain-level health rather than a specific subsystem.

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?

There is no statement of when to call this versus the other status/info tools in the catalog. The only routing sentence points at earning_opportunities, which is a cross-sell for a different task, not guidance on selecting this tool.

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