get_quote

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint. Description adds 'Returns real-time or latest close,' which clarifies timing behavior and is consistent 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?

Description is concise with a main statement, strategy, critical rule, and example. No fluff. Slightly longer than minimal but each part adds value.

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?

Simple tool with one parameter and output schema present. Description covers how to invoke, what it returns (real-time/latest close), and critical formatting rules. Adequate for the complexity.

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 has 0% coverage but description adds critical format rule for symbols ('<code>.<market> format'), which adds meaning beyond the schema's array of strings. Example further clarifies usage.

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?

Description clearly states 'Get latest quote snapshot for one or more symbols.' This specifies the verb, resource, and scope, distinguishing it from sibling tools like get_candlesticks or get_depth.

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?

Includes strategy ('Directly invoke with symbol list') and critical rule about symbol format ('must be .<market>'). Provides example. Missing explicit guidance on when not to use or alternatives, but sufficient for most cases.

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