List blockchains (P-Chain)

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

Annotations already indicate read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context about the return content (subnet and VM IDs) and the availability of filtering and pagination, which goes beyond the annotations without contradicting them.

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?

Two short sentences, front-loaded with the main action, and every phrase earns its place. No redundancy or 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?

The description covers the essential behavior and return info (subnet and VM IDs) for a list operation. Since there is no output schema, the mention of return fields is helpful. Network default is documented in the schema, so it does not need repetition. Overall it is adequate for correct invocation, though it could hint at pagination constraints or network selection.

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?

With schema description coverage at 50%, the description does compensate partially by mentioning 'name filtering' (mapping to name_contains) and 'pagination' (mapping to limit/offset). However, it does not explain the network parameter or elaborate on the specific semantics of parameters beyond what the schema already provides for network and name_contains.

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 states a clear verb and resource: 'List all blockchains registered on the P-Chain' with specific details about the output (subnet and VM IDs). It is specific enough to distinguish from sibling tools like avax_pchain_get_subnet, which focuses on individual subnet data.

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 its use case (listing blockchains) and mentions supports for filtering and pagination, but does not explicitly state when to use this tool versus alternatives or provide exclusions. No sibling differentiation is provided, leaving the agent to infer based on names.

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