Get Plan

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

With no annotations, the description carries the full burden. It discloses that markdown format is only available for finalized plans, which is useful behavioral context. However, it does not describe error behavior (e.g., what happens if session ID is invalid or plan not finalized for markdown) or authentication requirements.

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 two sentences, each serving a purpose. The first sentence states the primary function, and the second bulletizes the format options. No redundant or filler words.

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 the tool's simplicity (2 params, no output schema), the description is quite complete. It explains the purpose, required parameter, and format options with implications. However, it could benefit from clarifying what happens if a non-finalized plan is requested in markdown format or if the session ID is missing.

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 baseline is 3. The description adds meaning by explaining what each format returns: 'Rendered Markdown plan (default, only available for finalized plans)' and 'Raw JSONL event log (full session history for reconstruction).' This goes beyond the schema's simple enum description.

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 the purpose: 'Retrieve a saved deep_planning session by its session ID.' It uses a specific verb ('retrieve') and resource ('deep_planning session'), and distinguishes itself from sibling tools like list_plans which lists sessions, and deep_planning which creates them.

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 provides no guidance on when to use this tool versus alternatives, such as list_plans or promote_plan. It does not mention any prerequisites or conditions like requiring a finalized plan for markdown format, but fails to clarify when to use each sibling.

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