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

The annotations already declare readOnly and idempotent behavior. The description adds useful context by defining the semantic meaning of the two compatibility flags and calling out a specific chainId relevant to the drop feature, going beyond what hints alone convey.

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, information-dense sentence that front-loads the core purpose and then provides necessary clarification. There is no filler or redundancy; every clause earns its place.

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 explains what the tool returns (product chains with lookups and drop flags) and gives a concrete chain-id example for Solana, which is enough to understand typical usage. It does not mention pagination, but for a list of chains, that's likely nonessential.

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 accepts zero parameters, so the input schema carries no burden. The description correctly focuses on output semantics rather than parameter details, matching the baseline expectation for a no-parameter tool.

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 opening clause 'List product chains with per-feature compatibility' immediately identifies the action and object. It clearly distinguishes this tool from sibling operations by focusing on chain-level feature support rather than individual entity manipulation.

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 explains what 'lookup' and 'drop' flags mean)Skip which helps interpret results, but it does not explicitly state when to use this tool over alternatives or mention exclusion conditions. The reference to connect_drop / connect_drop_balance provides some navigational context, but it is incidental rather than prescriptive.

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