Get Subnet / L1 info (P-Chain)

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

Annotations already declare readOnlyHint=true, so the description does not need to restate read-only behavior. It adds value by detailing what the response includes (control keys, threshold, isPermissioned status, manager chain/address, blockchains), giving the agent a clear expectation of the returned data. It does not disclose error behavior or pagination, but for a simple getter with annotations covering safety, this is above average.

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 a single, front-loaded sentence that states the core action first and then packs the specific data fields delivered. Every clause earns its place—no filler, no redundancy. The structure makes it easy for an agent to quickly parse the tool's purpose and outputs.

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?

With no output schema, the description compensates by listing the key return fields (control keys, threshold, isPermissioned, manager, blockchains), which is sufficient for an agent to know what it will get. It does not cover error scenarios or edge cases (e.g., subnet not found), but for a simple read-only getter with only two well-documented parameters, this is nearly complete. Missing details like response format are minor.

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%: both 'network' and 'subnet_id' have descriptive comments. The description does not add any parameter-specific meaning beyond the schema; it only lists what data is fetched. Since the schema already explains the parameters, the description adds no extra semantic value, matching the baseline of 3.

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 opens with a specific verb-resource pair ('Get Subnet details') and then enumerates the exact data fields returned (control keys, threshold, isPermissioned, manager, blockchains). It also names the underlying platform.getSubnet call, which unambiguously identifies the operation and naturally distinguishes it from sibling tools like get_validators or get_balance.

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 no guidance on when to use this tool versus its siblings. It does not mention alternatives, exclusions, or prerequisites (e.g., 'use list_blockchains first to get subnet_id'). The purpose implies it is for subnet-specific details, but no explicit when-to-use or when-not-to-use guidance is given.

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