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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint, so the safety profile is covered. The description adds real value by disclosing what comes back (current open state plus session open/close times), which matters because there is no output schema. It omits operational details an agent may care about, such as timezone of the returned times, holiday/half-day handling, and whether the answer is cached or live.

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?

Two sentences, no filler: the first states the return content, the second the call condition. The most decision-relevant information (is the market open) is front-loaded.

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 read with no output schema, the description covers both the payload shape and the reason to call it. The only meaningful gap is not naming the timezone or exchange calendar conventions behind the session times, which leaves slight ambiguity about how to interpret the returned boundaries.

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 no parameters, so there is no parameter semantics to explain and the description does not need to compensate. Baseline of 4 applies for a zero-argument tool.

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 names a specific subject (US stock market) and states precisely what is answered: whether it is open now plus the current/next session's open and close times. No sibling tool covers market hours, so an agent can identify the right tool from the first clause alone.

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?

It gives explicit triggering conditions — 'check before stock analyses or autopilots that depend on market hours' — which tells the agent both the use case and the caller types that should gate on it. It stops short of saying when not to call (e.g. historical or post-hoc analysis), so not a full when/when-not/alternatives statement.

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