getNetworkStatus

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

With no annotations at all, the description must carry the behavioral burden. It discloses the payment/cost behavior ('free — no payment required') and the read-only nature implied by 'Get', but it does not clarify what the returned status contains or any rate limits/error behavior.

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; the parenthetical payment clarification is short and materially useful. Everything in the description earns its place.

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 parameterless status check, invocation is simple, but there is no output schema and the description does not explain what 'network status' includes (e.g., latest ledger, connectivity, health). An agent can call the tool without ambiguity, but it cannot predict or interpret the response with confidence.

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 input schema has zero properties, so there are no parameters for the description to explain and schema coverage is trivially complete. This matches the 0-parameter baseline, and no additional parameter detail is 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?

Names a specific resource ('Stellar network status') and a clear read verb ('Get'), which sets it apart from sibling tools that target accounts, ledgers, trades, and so on. The phrase 'network status' is still a bit underspecified—it does not define what facets are reported—so it stops short of a 5.

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?

The description implies the tool is for checking Stellar network status and adds the cost-relevant hint that it is free, but it never says when to prefer it over siblings or mentions any exclusion conditions. Context is present, but explicit selection guidance is absent.

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