get_agent_context

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

No annotations provided, so the description carries full burden. It discloses that frames are ground truth and captions/transcript are untrusted user speech, a key behavioral trait. It also notes inline images and click positions. While it doesn't cover auth or rate limits, the disclosure is adequate for a read-only tool.

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 somewhat long but every sentence adds value. The purpose is front-loaded with bold text, and details are listed efficiently. A minor improvement could be more brevity, but it's well-structured.

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 no output schema, the description thoroughly explains the bundle components (metadata, AI summary, action items, key moments with images, transcript). It also mentions a similar public document for reference, making it highly 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 already provides full coverage (100%), but the description adds value: for 'id', it explains it can be a slug or full URL; for 'maxFrames', it states a default of 6 and clarifies it's a cap on inline frame images.

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 that this tool returns a comprehensive context bundle for a recording, listing specific components (metadata, AI summary, action items, key moments with inline images, transcript). This distinguishes it from sibling tools that return individual pieces.

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 explicitly says 'Use this first when someone hands you a Clipy link and asks you to act on it,' providing clear when-to-use guidance. It lacks explicit when-not-to-use or alternative tool mentions, but the context is strong enough.

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