read_capture

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

No annotations provided, so description carries full burden. It discloses three modes with token cost implications and recommends starting with lighter modes. Does not mention read-only nature explicitly, but it's implied by 'Read'. No contradictions.

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, both front-loaded with essential information: purpose + use case in first, modes + guidance in second. No filler.

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?

Covers purpose, usage context, mode selection, and token cost. Lacks description of output format (e.g., whether it returns text/JSON), but given no output schema, the modes imply the output type. Nearly 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 coverage is 100%, but description adds significant value: elaborates on mode options with token cost and usage strategy, and clarifies id parameter source ('from list_captures').

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?

Description clearly states 'Read a PreCompact capture by ID' and provides the specific use case 'recover context that was lost during mid-session compaction', distinguishing it from siblings like list_captures and capture_now.

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 says when to use (recover lost context) and provides mode guidance ('Start with the lightest mode that answers your question'). Lacks explicit 'when not to use' or sibling alternatives, but the guidance is clear.

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