get_event_snapshot

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

The description adds the key detail that the output is a base64-encoded JPEG, which is useful. However, with no annotations, the description carries the full burden and does not mention any potential errors, permissions, size implications, or side effects. Since this is a simple 'get' operation, the lack of mutation cues is implied, but not fully transparent.

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 directly states the action and result format. No filler or redundant information, every word is necessary.

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?

For a simple retrieval tool with fully described schemas and an output schema present, the description is nearly complete. It lacks only usage context to differentiate from sibling tools, which prevents a perfect score.

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 all three parameters (event_id, crop, quality), so the description adds no additional parameter semantics beyond the schema. The baseline of 3 applies because the description does not compensate with extra details.

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 a specific action ('Get the snapshot image for an event') and the result format ('base64-encoded JPEG'). However, it does not explicitly distinguish this from sibling tools like get_event_thumbnail, whose purpose is likely similar.

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?

No guidance is provided on when to use this tool versus alternatives such as get_event_thumbnail or get_event. There is no mention of appropriate scenarios, exclusions, or prerequisites, leaving the agent to infer usage.

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