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

With readOnlyHint=true already declared, the safety profile is covered; the description adds the genuinely useful 'Cached ~60 seconds' freshness bound, which tells the agent how stale the data may be and discourages rapid re-polling. It does not describe the response shape, but caching detail is the key behavior for a pulse-style endpoint.

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?

One sentence, front-loaded with the resource and scoping, then the payload contents, then the caching caveat. Nothing is wasted and nothing important is buried.

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?

There is no output schema, so the description must carry the return-shape burden, and it does by listing session state, three ETF quotes, and news. Coverage is good; minor gaps remain about how many news items or quote fields are returned, but nothing blocks a correct call.

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 schema defines zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly signals that the tool is parameterless and returns a fixed bundle.

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 the resource (US market status) and enumerates exactly what comes back: session state, SPY/QQQ/DIA prices with % change, and top news. This is specific enough that an agent can distinguish it from get_ticker_snapshot or get_daily_brief, though it never names a sibling explicitly.

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?

There is no when-to-use guidance, no stated preconditions, and no routing to alternatives such as get_ticker_snapshot for a single symbol or get_sector_sentiment. The agent must infer timing from the word 'Current' alone.

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