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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the notion of 'relative trade activity' but does not disclose additional behavioral traits such as ranking order, inclusion criteria, or whether results are based on the selected window. It is consistent with annotations but does not go beyond them meaningfully.

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, front-loaded sentence with no filler. It states the core purpose in ten words and earns its place in the definition.

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 read-only tool with two optional self-explanatory params, the description is minimally adequate but leaves gaps: it gives no sense of the result format, the meaning of 'relative trade activity', or how the window parameter affects behavior. Annotations cover safety, but an agent would still need to infer operational details.

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 0%, so the description must compensate by explaining what `limit` and `window` mean in context. It does not mention either parameter at all, leaving an agent to infer semantics only from names, defaults, and enum values. No added meaning is provided beyond the 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?

The description states a clear action ('find symbols') with a specific qualifier ('highest relative trade activity'), making the core purpose understandable. However, it does not distinguish this tool from close siblings like get_top_momentum or find_unusual_activity, so an agent may struggle to choose between them without opening schemas.

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?

There is no guidance on when to use this tool versus its many siblings, nor any explicit exclusions or context. The description only states what it does, not when it should be selected over alternatives like find_strong_buying or get_top_momentum.

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