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

The description discloses key behavioral traits: it is a read operation ('Read'), uses an external data source ('Uses Yahoo Finance'), and omits missing trading days. Since annotations provide no readOnlyHint or destructive flags, these details help set expectations.

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 concise, front-loaded with the primary purpose, and contains no extraneous information. Two sentences suffice to convey the core functionality and key caveats.

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?

The description is adequate for basic invocation but lacks details about return format and pagination behavior despite having limit/offset parameters. Given no output schema, the description could have briefly mentioned what is returned (e.g., date/price pairs) to be more self-contained.

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 input schema covers 80% of parameters with descriptions, but the tool description adds only marginal context (range limit, omission of missing days). The offset parameter remains undescribed, and the description does not clarify pagination semantics beyond what is in 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 clearly states the action ('Read daily closing prices'), the resource (a supported instrument), and the scope (a range of up to 366 days). This distinguishes it sufficiently from sibling tools like markets_quote or markets_convert.

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?

No explicit guidance is given about when to use this tool versus alternatives such as markets_quote for current prices or markets_list for supported symbols. The description implies historical use via 'daily closing prices' but does not name alternatives or conditions.

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