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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a non-mutating, read-only nature and rules out quoting/swapping, which is useful, but says nothing about authorization, rate limits, or what the balance read returns.

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 tight sentences with the purpose front-loaded and the routing note immediately after. No filler, and every sentence adds a distinct piece of information.

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 two-parameter read tool with no output schema, purpose and a key routing rule are covered. The main omission is any explanation of the 'symbols' filter, which leaves the agent guessing at that parameter's behavior.

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 only 50%: 'owner' is documented as a wallet address in the schema, but 'symbols' has no description anywhere. The description never mentions either parameter, so it fails to compensate for the undocumented array filter.

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 gives a specific verb+resource ('Read balances') and explicitly distinguishes the tool from trading siblings by stating it 'does not quote or swap.' It stops short of a fully self-contained statement of what 'holdings/value' returns, but an agent can place it correctly.

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?

It supplies an explicit when-not ('does not quote or swap') and names the alternative path ('use stocktoken_quote then stocktoken_execute_plan'). It does not address the other read-oriented siblings (e.g. stocktoken_get, stocktoken_morpho_position), so routing is clear for the trade case only.

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