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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds useful content detail about what the response includes, but it does not add behavioral context such as return format, freshness, or how peer details are represented.

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?

It is two tight sentences with the return contents front-loaded and a brief usage note second. There is no filler and no repetition of the tool name.

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 simple no-parameter read with no output schema, the description gives sufficient context by naming the main fields returned. It could be more complete by specifying the response shape or whether peer details include addresses, but nothing critical is missing for invocation.

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, so there are no parameter semantics for the description to explain. The baseline for a no-parameter tool is 4, and the description introduces no misleading parameter expectations.

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 gives a specific verb and resource: 'Returns network information' and then names the key contents (listening status, connected peers, peer details). It is clear what the tool does, but it does not distinguish itself from closely named siblings such as get_cometbft_status or get_network_info.

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 phrase 'Useful for monitoring P2P network health' implies a usage context, but there is no explicit guidance on when to choose this tool over alternatives and no exclusions. The agent is left to infer when this is preferable to get_cometbft_status or get_network_info.

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