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

Adds genuinely non-schema information: the call is free, it depends on previously stored exchange keys, and it returns only the list of refreshed exchanges, never an amount. With no output schema present, that return-value disclosure is the description's most valuable contribution. It does not cover partial-failure behavior when one exchange rejects the stored key, which keeps it from a 5.

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?

Three short sentences: action and data source first, cost second, return shape last. Nothing is repeated from the title or annotations, and every clause carries information the agent needs.

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?

Zero parameters and no output schema mean the description must carry the return contract, which it does ('which exchanges were refreshed, never an amount'). Safety profile is already handled by the annotations (non-read-only, idempotent, non-destructive, open-world), so nothing material is missing for correct invocation.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids restating an empty schema.

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 a specific verb (refreshes) and resource (member's balances) plus the exact source (exchanges connected in AstraEye, using stored keys). No sibling tool touches balances, and the phrase 'so research uses current holdings' frames the downstream effect, so an agent can select it without ambiguity.

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 trigger condition — call it before research so holdings are current — and no sibling competes for that role. It stops short of explicit when-not guidance (e.g., how often to refresh, what to do if an exchange key is stale), so it lands just below the top band.

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