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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds non-obvious behavior: the per-row return shape (score, band, counted patterns, coverage note) and status codes such as no_pool, no_candles, too_little_history, collecting. It also notes no API key is needed and points to chart_analyzer_study for the methodology.

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?

Dense but front-loaded: the batch scope and item forms come first, then the gem_screener alternative, then output behavior. The closing 'Not financial advice' is boilerplate that does not earn its place, but overall there is little waste.

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 compensates by summarizing row fields and no-score statuses, plus noting the 300-item cap and the study reference for pattern rates. An agent has everything needed to invoke and interpret this batch tool correctly.

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%, so a 3 is the baseline, but the description adds real meaning: items accepts either {contract, chain} or {symbol} forms, all rows use one timeframe, and gem_screener replaces items entirely. That clarifies how the parameters interact beyond the schema text.

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 a specific verb and resource with scope: 'Score many charts in one call (up to 300)'. It is clearly the batch counterpart to chart_analyzer_score and also covers the gem_screener mode, so an agent can distinguish it from siblings 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?

Explains the two selection modes (items list vs gem_screener=true) and the 'many in one call' context that selects batch over single scoring. It does not explicitly name chart_analyzer_score as the alternative for one-off lookups, leaving that inference to the agent.

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