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

Annotations already cover readOnly/idempotent/openWorld, but the description adds substantial behavior beyond them: the full status enum, which accounts are silently omitted, the failed_accounts error semantics and retry advice, what opens_at means, the absence of calldata/prices/simulation, and the Robinhood empty-list behavior. This is exactly the context annotations cannot 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?

Purpose is front-loaded and every paragraph carries operational content, but the description is dense and long, with an especially convoluted sentence about automations still running on old Slipstream managers. Nothing is truly waste, yet readability suffers compared to a tighter 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?

Despite an output schema existing, the description covers the edge cases an agent actually needs: empty-vs-failed distinction, excluded accounts, chain coverage, and handoff to the write tool. Nothing required to call or interpret it correctly 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?

Schema description coverage is 100%, so all three parameters are already documented, including the wallet/account exclusivity. The description repeats that exclusivity and the chain meaning (Robinhood yields an empty list) but adds little syntax or format detail beyond the schema, so baseline 3 applies.

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?

States precisely what is checked: Arcadia accounts with upgradeable Aero positions (Slipstream V1->V3, old AERO), with scope qualifiers (chains, staked or not). It explicitly names the sibling it is not — 'For the plan and the transaction call write_account_aero_upgrade' — so the agent can distinguish check from execution without opening a schema.

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 the routing rule between wallet_address and account_address, states when to escalate to write_account_aero_upgrade (including the specific case where read_asset_manager_current shows only metadexcl_v1 positions), and warns that an empty accounts list only means 'nothing to do' when failed_accounts is also empty. Alternatives and conditions are explicit, not inferred.

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