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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful scope by saying it returns the user's own rules and triggers awaiting action, but it does not mention pagination, filtering, or result shape.

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?

Two short sentences, front-loaded with what is returned and then the requirement. The first sentence is a fragment and the parenthetical is slightly compressed, but there is no filler.

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 simple one-parameter read tool with strong annotations and no output schema, the description covers the core return scope and required input. It could be stronger on pending-action status or filtering, but nothing critical to invocation is missing.

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?

There is one required address parameter with 0% schema description coverage. The description compensates minimally by identifying it as the wallet address needed for the lookup, though it does not clarify whether it is the connected user's wallet or any wallet.

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 identifies the returned resource as the user's Autopilot rules plus pending triggers/prepared actions to review and sign. The tool name supplies the list verb, but the description does not explicitly differentiate this from design_strategy or prepare_* siblings.

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 only states the wallet-address prerequisite and gestures at reviewing/signing prepared actions. It does not say when to call this versus design_strategy or other preparation tools, and it names no exclusions or alternatives.

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