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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavioral facts: the once-per-session call frequency, the prerequisite ordering, and the failure mode if omitted ('Time-series queries will timeout or return wrong results'). It also discloses the approximate payload (23 patterns) and their subject areas.

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?

Front-loaded with the critical constraint ('REQUIRED before stock_data_query'), which is exactly right for an agent scanning for gating conditions. Slightly weakened by repetition — the timeout/wrong-results warning appears twice — plus a second list of workflow mechanics that partly restates the opening line.

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 zero-parameter, no-output-schema utility tool, the description covers purpose, prerequisites, follow-up, and content categories well. It stops short of saying what the returned artifact actually looks like (raw SQL snippets, named patterns, JSON vs text), which an agent with no output schema would benefit from knowing.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing parameter-related to clarify, and the description correctly spends no words on arguments.

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 action (loading 23 SQL query patterns) plus the concrete content covered: time-series selection, return calculations, screening joins, window functions, backtesting, performance optimization. It also distinguishes itself from siblings by naming stock_data_query and get_database_schema as its workflow neighbors.

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?

Explicit sequencing: 'Must be called once per session immediately after get_database_schema', 'REQUIRED before stock_data_query', and 'After this tool returns, call stock_data_query'. The condition that determines calling it (querying stock data) and the penalty for skipping it (timeouts or wrong results) are both stated.

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