get_shot

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

With no annotations provided, the description carries the full burden. It discloses the specific output fields and the special behavior of omitting the ID to return the latest shot. It does not mention potential errors or read-only guarantees, but 'retrieve' implies a safe read operation.

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 two sentences, front-loaded with the primary purpose and enough detail to be immediately useful. Every sentence earns its place, with no filler or redundancy.

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 optional parameter and no output schema—the description covers the function, return data fields, and usage conditions effectively. It compensates for the lack of an output schema by listing expected return values, though it stops short of describing the exact data structure.

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 100% for the single 'id' parameter, describing it as a Shot ID and noting to omit for the latest shot. The description repeats this 'omit' behavior in prose but adds no new semantics beyond the schema.

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 states 'Retrieve detailed shot data with time-series curves for analysis,' which is a specific verb and resource. It lists the exact data fields returned, clearly distinguishing it from sibling tools like get_status or get_profiles.

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 provides clear context for when to use the tool ('for analysis') and gives a specific usage condition ('Omit ID to get the most recent shot'). It does not explicitly mention alternatives, but the context is enough to infer proper use.

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