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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds the returned fields and workflow placement. It says nothing about pagination, result size, or how the optional filter affects the 'every symbol' claim, so it adds only moderate context.

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: the return content is front-loaded and the call-timing guidance follows immediately. No filler text at all.

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?

With no output schema, the description does the needed work by enumerating the key returned fields and the call timing. The only real gap is the asset_class filter, which an agent using this tool would likely want explained.

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 single asset_class enum parameter has 0% schema description coverage and is never mentioned in the description. Worse, 'Every tradable symbol' arguably implies results are unfiltered, which sits awkwardly with the optional filter, so the description neither explains nor compensates for the parameter.

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 the resource precisely ('every tradable symbol') and names the returned attributes (asset class, max leverage, taker fee), which lets an agent tell it apart from price/screener siblings. The verb is only implicit, but the scope is unambiguous.

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?

'Call this before sizing a trade' gives a clear contextual trigger tied to a downstream workflow. It does not name alternatives such as get_screener or get_price, nor say when this is not needed, so it falls short of the 5 tier.

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