Get full clip

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

With no annotations, the description carries the behavioral burden and does well: it explains that content is full and untruncated, describes per-type return content, and explains how to resolve screenshot blob hashes. It does not explicitly mention permissions or error behavior, but 'fetch' adequately signals a 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 dense but well-structured: it front-loads the core purpose, then organizes details by entity type. Every sentence carries useful selection or interpretation information for a polymorphic retrieval tool.

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?

Without an output schema or annotations, the description compensates by explaining return content for each entity type and how to resolve blob hashes. An agent should be able to call this correctly and interpret the results from the description plus schema.

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%, so the schema already documents all three parameters. The description adds value beyond the schema by clarifying type-specific behavior, especially what recording transcript_segments provide and that include_context applies to clips.

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 a specific verb and resource: fetch one clip, recording, screenshot, or transcription by id with full content. It clearly distinguishes this full-detail retrieval from search/recent by saying to use it after those tools return an id.

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?

It explicitly routes the agent: use after eve_search/eve_recent returns an id. It also names the downstream relationship to eve_export_clip for recordings, making the workflow position clear.

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