Get Snapshot Price

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds 'no subscription side effects' which is valuable behavioral context beyond annotations. No contradictions.

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 concise sentences that front-load the main action ('Fetch a snapshot...') and add a clarifying note. No unnecessary words.

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 five parameters, no output schema, and no parameter descriptions, the description is too brief. It does not explain return values, parameter meanings, or any constraints (e.g., what fieldGroups does). Insufficient for an agent to use correctly without additional knowledge.

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%, so the description must compensate but does not explain any of the five parameters (uic, assetType, accountKey, amount, fieldGroups). Parameter names are somewhat self-explanatory but not formally described, leaving ambiguity for the agent.

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?

Clearly states 'Fetch a snapshot bid/ask/last price for a single instrument' and distinguishes from sibling 'saxo_get_infoprices_list' by noting it is for a single instrument. Also adds 'Snapshot only — no subscription side effects' to further clarify scope.

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?

Explicitly says 'Snapshot only — no subscription side effects,' implying use for one-time price retrieval without starting a subscription. Differentiates from list version implicitly. However, no explicit when-not-to-use or comparison to other related tools like charting tools.

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