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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the description's added value is the entitlement note ('Answers any account, free included') and the scope note that it works for both US and Europe symbols. That goes beyond what the structured fields say, though it says nothing about failure modes or rate limits.

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?

One sentence, front-loaded with the purpose, then a compact enumeration of what comes back. It is dense but every clause maps to a returned field or an input constraint, and there is no filler or restating of the title.

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?

There is no output schema, so the description must carry return-value semantics, and it does: pivot zones, daily/weekly/monthly opens with sigma bands and EMAs, prior close, 52-week range, and pick target/stop. Missing only hints about response shape or empty/no-data behavior for an unknown ticker.

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 100% and the single parameter is documented as a US ticker (NVDA), so the baseline is 3. The description adds real meaning by extending acceptable input to Europe symbols and giving the concrete format 'AIR.PA', which the schema does not cover.

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?

Opens with a specific verb+resource ('The full levels for one name') and then enumerates the returned fields, so an agent knows this is the aggregated levels endpoint rather than a profile. It does not name or contrast with the closest sibling (ticker_profile), which keeps it just short of a 5.

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?

Usage is implied by the phrase 'Answer any account, free included' and by the enumeration of levels-style content, so an agent can infer this is the levels lookup. There is no explicit when-to-use/when-not or reference to an alternative sibling such as ticker_profile or screen.

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