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

With no annotations provided, the description carries full responsibility for behavioral transparency. It only lists acceptable assets and does not disclose whether the operation is read-only, requires authentication, returns static or live data, or any side effects. This is insufficient for an agent to fully understand the tool's behavior.

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?

The description is a single sentence with no wasted words. It is front-loaded with the key information about what the tool returns. Every part of the sentence contributes to understanding the tool's purpose.

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 tool with no parameters and no output schema, the description is fairly complete. It tells the agent what the tool returns. However, it could be more explicit about the output format or that no input is required, which would make it even more self-contained.

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 are no parameters in the input schema, so schema coverage is 100%. The description adds meaning by specifying what the tool returns (list of accepted assets). It provides context beyond the empty schema, earning a baseline 4.

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 clearly states what the tool does: it enumerates the assets that the AATOS tip wallet can accept, specifically native ETH, any ERC-20 on Robinhood Chain 4663, and optionally native BTC. This distinguishes it from sibling tools like stocktoken_tip_plan and stocktoken_tip_presets, which handle other aspects of tipping.

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 implies that the tool is used to check acceptable assets before tipping, but it does not explicitly state when to use it versus alternatives, nor does it provide any exclusions or prerequisites. For a tool with many siblings, more guidance would be beneficial.

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