Get a market quote

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that data comes from a configured data source or loaded local bars, which is a useful source context but does not disclose further behavioral traits such as return format or failure modes. No contradiction with annotations.

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 a single concise sentence that directly states the action and source. Every word earns its place, and the key information is front-loaded with 'Get one current quote'.

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?

Given the tool's simplicity, the description provides a basic understanding of what it does and its data source. However, the lack of parameter explanations for fields and session, combined with no output schema, leaves some gaps. Annotations fill the safety context, but a more complete description would clarify the fields parameter.

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 coverage is only 33% (only symbol has a description), leaving fields and session undocumented. The description mentions 'snapshot fields', which loosely relates to the fields parameter, but it does not explain the valid values or the meaning of the session parameter. The description only partially compensates for the low schema coverage.

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 the tool retrieves a single current quote and snapshot fields, and the word 'one' differentiates it from the sibling tool market_get_quotes. However, 'snapshot fields' is somewhat vague and does not specify what fields are included or how they are selected.

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 description implies usage for a single quote, contrasting with the plural sibling 'market_get_quotes', but it does not explicitly state when to use this tool over alternatives like market_get_price or market_get_capabilities. No exclusions or alternative recommendations are provided, only the implied context of a single quote.

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