get_market_state

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds meaningful behavioral context: the response includes a freshness verdict and a usable_for_analysis field that must be checked before relying on the value, implying staleness is possible. This is genuinely informative, though it could also state read-only guarantees or error behavior.

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 two tight sentences with the core purpose front-loaded and a critical usage caveat included. There is no filler or redundant information.

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 one-parameter tool with no output schema, the description gives essential freshness-checking guidance but does not explain what the market state payload actually contains or what other fields to expect. An agent can call it correctly but may not fully understand the response beyond the freshness verdict.

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 0% and the description only restates that the tool works 'for a symbol' without adding format, examples, or accepted value conventions. It adds no real semantic value beyond the schema's property name and type.

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 that the tool returns the current market state for a symbol and flags an explicit freshness verdict. It identifies the resource and the nature of the result, though it does not explicitly distinguish itself from siblings like get_recent_bars or get_feed_health.

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 guidance on when to use this tool instead of its siblings, nor any exclusions or alternative routing. The advice to check freshness.usable_for_analysis is useful after the call but does not help an agent decide when to invoke this tool.

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