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

With no annotations, the description carries the full burden. It accurately signals a read-only retrieval operation and specifies exactly what data is returned. It does not mention rate limits, error conditions, or data freshness, but for a simple zero-parameter getter these omissions are minor.

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?

A single sentence that front-loads the action ('Retrieve') and resource, lists the key data types, and scopes the result to all 4 chains. No filler or redundant phrasing.

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 zero-parameter, low-complexity tool with no output schema, the description gives enough information about what will be returned to guide correct use. It could name the specific chains or return field names, but it is not critically incomplete.

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 has zero parameters, so the baseline is 4. The description adds relevant context about what the resulting data conveys, even though there is no parameter detail to supplement.

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 ('Retrieve') with a concrete resource: technical network specifications, Chainlink CCIP selectors, router contracts, and registry addresses for all 4 supported chains. This clearly distinguishes it from sibling tools, which focus on domain registration, resolution, and marketplace operations.

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 intended use is implied by the tool's name and description: call it when you need chain network specifications or contract addresses. However, there is no explicit statement about when to use it over alternatives, though none of the siblings appear directly comparable.

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