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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is elsewhere — it does add it: the empty-list-means-none versus oracle-failure-is-an-error distinction is a behavioral trait an agent would otherwise misread. It doesn't mention latency or rate limits on the cross-chain fan-out, which for an openWorld multi-chain read would be useful.

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?

Front-loads the resource and scope, then closes with the routing hint and the empty-versus-error caveat; every clause carries information. It runs a bit long as three dense ideas in two sentences, but nothing is wasted.

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 one parameter, no output schema, and read-only annotations, the description covers what the agent needs: scope, exclusions, result shape (app link per entry), and empty-versus-error semantics. Return structure beyond 'app link for each' is left implicit, which is acceptable for a list tool.

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 100% and the single `owner` parameter is fully documented in the schema, including the EOA-or-smart-account note, so the description adds little parameter-level meaning. Baseline 3 applies when the schema already carries the semantics.

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?

Names a concrete resource (unisafe LP managers, Stable and Volatile) with scope defined as every chain the Envelop oracle indexes, and explicitly carves out what is excluded (other Envelop wNFTs). The phrase 'the way in when you know the owner and not the managers' separates it from the sibling list_operators that would answer a different question.

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?

Gives a clear selection rule ('when you know the owner and not the managers') and states the exclusion of other Envelop wNFTs, so the agent knows when this list is the right one. It does not name list_operators or the inverse lookup case explicitly, so the routing is implied rather than complete.

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