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

No annotations are provided, so the description carries the full burden. It discloses caching behavior ('Cached 30 seconds'), authentication ('Free, no auth'), and all returned fields. It also mentions API key retrieval for direct calls, which adds useful context. Minor omission: no mention of rate limits or potential throttling.

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 slightly verbose (5 sentences) but well-structured: it front-loads the purpose and key metrics, then provides caching and auth info, then usage guidance, and finally API key retrieval details. The API key info could be considered secondary but is relevant for power users.

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?

Given it has no parameters and no output schema, the description covers all necessary context: what the tool returns, how to interpret results, caching behavior, authentication, and even the threshold for network stress. It is entirely self-contained and leaves no ambiguity.

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 parameters with 100% schema description coverage, so baseline is 3. The description does not need to add parameter information. It correctly refrains from repeating what the schema already conveys.

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 clearly states 'Live Monad mainnet network stats via NadCity' and lists specific metrics. It distinguishes from siblings by focusing on a specific niche (Monad network health) and explicitly states the use case. While 'monad_city' is a sibling, the description's specificity makes the purpose unambiguous.

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 explicitly states when to use: 'Use before any on-chain Monad action to check network health.' It provides actionable thresholds: 'If avgBlockTimeMs > 500 or wsConnected is false, the network is under stress.' This gives clear guidance on interpretation and usage context.

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