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

With no annotations, the description carries the burden and does well: 'FREE, no key' covers auth/cost, and 'Holidays and half-days not included' is a material scope caveat that prevents wrong conclusions. It still omits return format and timezone semantics, keeping it from a 5.

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 cost/auth qualifier, then the core question, then scope and the market list. The long exchange enumeration is informative rather than filler, though slightly list-heavy.

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-required-parameter read tool, it discloses coverage limits, supported markets, and hints at 'next open/close'. With no output schema, it should say more about the response shape, but overall it is nearly sufficient.

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 description coverage is 100%, so the schema already documents 'at' (ISO time, default now) and 'market' ('all' or codes). The description only loosely gestures at these ('at a given time', the market list) without adding syntax beyond the schema; baseline 3 applies.

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 ('Is a stock exchange open now (or at a given time)?') and enumerates the covered exchanges, so the agent knows exactly what it does. It does not explicitly distinguish itself from the sibling forex_market_hours, so it stops 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 only implied by the phrasing 'open now (or at a given time)' and the market list. There is no explicit when-to-use/when-not guidance and no routing to the nearby forex_market_hours alternative.

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