resume

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

No annotations are provided, so the description carries the full burden. It lists exactly what data is fetched (tabs, scroll positions, video timestamps, etc.) and states it returns the full Resume Context. This is substantial behavioral context, though it does not explicitly state whether the operation is read-only or what permissions are needed.

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 sentences, no unnecessary words. The first sentence front-loads the purpose and what the tool returns. The second sentence is a crisp usage instruction. Every part earns its place.

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 adequately explains what is returned (list of components). The parameters are fully covered by the schema, and the tool's purpose and usage are clear. No gaps remain for an AI agent to select and invoke this tool correctly.

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 baseline is 3. The description adds value by aligning the listed fetched data with the possible values of the 'include' parameter (tabs, media, reasoning_thread, ai_tags), implicitly clarifying what each option does. This goes beyond the schema descriptions.

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 verb 'Resume' and resource 'UNIHODL session' are specific. It clearly distinguishes from sibling 'list_sessions' by describing that this tool fetches session context rather than listing sessions.

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 states 'Call this before any other tool when given a session_id', providing clear guidance on when to use this tool and implying the order of operations. No exclusion or alternative is needed given the context.

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