get_shot_details

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

With no annotations, the description carries full burden. It discloses that the tool returns 'complete timeseries data' but does not mention side effects, authorization requirements, or behavior on invalid IDs. The read-only nature is implied but not explicit, making transparency adequate but not outstanding.

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 clearly states purpose and key details, the second provides actionable usage guidance. No waste, front-loaded with critical information.

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 (one parameter, no output schema), the description covers purpose, how to get the input, and what data is returned. Missing details on the structure of the timeseries data or error behavior, but overall sufficient for a straightforward retrieval tool.

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?

The schema already provides 100% coverage for the single parameter, describing it as shot ID (uuid or number). The description adds value by linking to search_shot_history for obtaining IDs but does not enhance parameter semantics beyond the schema, meeting the baseline for high 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 full details for a specific shot by ID, including complete timeseries data. This distinctly differentiates it from sibling tools like search_shot_history (which finds IDs) and get_current_shot/get_last_shot (which get specific shots without full timeseries context).

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 advises using search_shot_history first to obtain shot IDs, providing clear prerequisite guidance. Does not include explicit when-not-to-use instructions, but the context is strong enough to inform correct usage.

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