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

No annotations are provided, and the description only states the lookup target and output categories. It does not disclose safety, permissions, default network behavior, possible edge cases (e.g., unknown ID), or response format, placing the full burden on the description and falling short.

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 sentence with clear, front-loaded structure. It avoids extra words and communicates the core purpose efficiently.

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 two-parameter lookup tool, the description provides the essential purpose and return categories, but lacks details on default network, error behavior, and response structure. Given the absence of annotations and output schema, the description is minimally adequate but not fully complete.

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 coverage is 50%, with only subnetId having a description (and that description is trivial). The description does not explain the network parameter at all; it only refers to 'by its ID,' which adds no meaning beyond the schema. The enum values are present but not semantically explained.

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 a specific verb ('Look up') and resource ('Subnet / L1') by ID, and lists the returned data ('validators, chains, and configuration'). This clearly distinguishes it from sibling tools like blockchain_lookup_chain or blockchain_lookup_validator.

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 usage when you have a Subnet ID and need details, but it does not explicitly state when to use this tool over alternatives, nor does it mention relevant siblings such as platform_get_subnets or blockchain_lookup_chain. The context is clear but lacks explicit guidance.

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