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

With no annotations, the description must disclose behavior itself. It says 'this node is participating in', implying the return value depends on the node's current network, but the optional 'network' parameter suggests a default of 'mainnet' per the schema. This conflict creates ambiguity about what the tool actually returns when no parameter is supplied.

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 extremely concise at 14 words, front-loads the key action, and contains no filler. It is appropriately sized for a simple getter tool.

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 getter, the description covers the essential purpose and the schema defines the parameter. However, it leaves ambiguity about the default behavior and the format of the return value, and lacks any clarification of edge cases. More context would be needed to fully guide the agent, especially given the lack of annotations.

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?

Schema description coverage is 100%, so the parameter is already well-documented. The tool description adds the phrase 'this node is participating in', which creates ambiguity rather than adding clarity about the parameter's role. It adds limited value and potentially confuses the default behavior.

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 uses specific verb 'Get' and resource 'human-readable name of the Avalanche network', clearly distinguishing it from sibling tools like info_get_network_id that likely return numeric IDs. It precisely states what the tool does.

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 provides clear context for when to use the tool (when you need the network name), but it does not explicitly mention alternatives or exclusions. The context is self-evident, but no when-not guidance is given.

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