get_crypto_snapshot

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

With no annotations, the description carries full burden. It discloses a critical constraint (loc must always be 'us') and lists the included data components, but does not mention safety profile, rate limits, or response format beyond what the output schema already covers. It is adequate but not comprehensive.

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: the first states purpose and contents, the second gives a specific parameter instruction. No unnecessary words, and the most important usage constraint (loc='us') is front-loaded.

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?

The description covers the tool's main purpose and a key constraint. Since an output schema exists, return structure is already documented. It lacks a note about sibling tools or when not to use it, but for a straightforward snapshot read operation, it is largely complete.

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 100% for both parameters. The description adds value by emphasizing that loc is required and should always be set to 'us' (despite other enum options), and clarifies that symbols accepts one or more comma-separated crypto symbols, enhancing parameter understanding.

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 returns a snapshot for one or more crypto symbols, listing its contents (latest trade, quote, minute bar, daily bar, previous daily bar). This specific verb+resource+scope distinguishes it from sibling tools like get_crypto_latest_trade or get_crypto_bars.

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 gives a clear usage instruction for the loc parameter ('always set loc to "us"'), which is helpful. However, it does not explicitly mention alternatives or when to use this tool versus sibling snapshot-related tools, so usage guidance is implied rather than explicit.

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