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

Annotations already establish read-only, idempotent, non-destructive, and non-open-world behavior. The description adds meaningful domain behavior beyond those annotations: price feeds pause at the last print during market closure, the weekend price is not read on chain, and a market clock is included. It still lacks error behavior when the market is open and freshness/update details.

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 compact and front-loads the market-closed condition, with each sentence contributing needed output scope. However, the long clause-heavy 'For each stock...' list is dense and would be easier to scan as structured bullets.

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 complex weekend/off-chain data tool with no output schema, the description covers the main returned datasets and the important off-chain caveat. It still omits the exact response shape and what happens outside the weekend window, so it is not fully complete.

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 single optional symbol parameter is fully documented in the schema with 100% coverage. The description's phrase 'For each stock' hints that omitting the symbol may return all stocks, but it does not explicitly define the optional parameter behavior beyond what the schema already states.

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 identifies a specific data resource: weekend paused prices, Borro's weekend price and 95% band, Monday gaps, gap cover quotes, market clock, and pool details. It does not use a direct verb such as 'returns' and does not name sibling alternatives like prices or market, so it falls 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?

The opening clause implies this is for use while the stock market is shut (Friday 8pm to Sunday 8pm New York, and holidays), but there is no explicit when-to-use/when-not-to-use guidance or named alternative. The line 'Nothing on chain reads the weekend price' is a caveat, not a routing rule.

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