Get Snapshot Prices (List)

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

Annotations (readOnlyHint, non-destructive, idempotent) already indicate a safe read operation. The description adds that this fetches snapshot prices, aligning with annotations. No contradictions, and it hints at the batch capability, but additional details (e.g., caching behavior) are absent.

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, front-loaded sentence that efficiently conveys the core purpose. However, it could be slightly more detailed about parameters without becoming verbose.

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?

No output schema or return value description exists. The description does not clarify optional parameters like accountKey or fieldGroups, nor their impact on results. Given the tool's complexity (multiple Uics, asset types), the description is insufficient for complete understanding.

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 0%, and the description does not explain any of the four parameters (uics, assetType, accountKey, fieldGroups). Without additional context, the agent cannot infer parameter meaning, which is critical for correct invocation.

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 action ('Fetch snapshot prices'), resource ('multiple Uics'), and batch nature ('in one call'). This distinguishes it from the sibling tool 'saxo_get_infoprice', which likely handles a single Uic.

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 batch price retrieval but does not explicitly state when to use this tool versus alternatives like 'saxo_get_infoprice' or other data tools. No exclusions or prerequisites are mentioned.

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