pull_session

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

With no annotations provided, the description fully discloses key behaviors: short sessions return full transcript automatically, long sessions return summary + recent turns, and the agent MUST ask the user before proceeding on a summary. It also instructs to call again with full=true only after confirmation. This is exemplary transparency.

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 filler. The purpose is front-loaded, and the conditional behavior is explained in a structured, easy-to-follow manner. Every clause 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?

Despite lacking an output schema and annotations, the description covers the main decision flow, parameter usage, and the critical user-confirmation requirement. It is complete enough for an agent to select, invoke, and correctly handle the tool's results.

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?

The schema already provides detailed descriptions for both parameters (100% coverage), so the baseline is 3. The description adds contextual semantics by explaining that full=false is the observed behavior for longer sessions and that full=true should be used after user confirmation, going slightly beyond the schema's wording.

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: 'Pull a shared agent session (by share link or token) into the current conversation to continue or build on it.' It clearly distinguishes from sibling tools (list/search/share/unshare) by focusing on importing a shared session.

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 explains when to use the tool (to continue/build on a shared session) and gives important procedural guidance for short vs. long sessions, including mandatory user confirmation. It does not explicitly name alternatives or state when not to use it, but the context and sibling tool names make the usage clear.

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