capture_now

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

Discloses file creation location, artifact equivalence with PreCompact, and optional parameters with auto-discovery. No annotations provided, so description carries full burden. Could mention idempotency or error handling but still provides solid behavioral context.

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. First sentence clearly states action and output. Second provides usage and parameter notes. Perfectly front-loaded and efficient.

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?

Describes artifact and auto-discovery for parameters, but does not explicitly state return value or success indication. With no output schema, the description could mention what the tool returns (e.g., path to capture). Still, very informative overall.

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?

Input schema has 100% description coverage. Description adds value by noting that session_id and transcript_path can be omitted and auto-discovered, going beyond schema. Reason parameter is not elaborated in description but schema covers it. Extra context earns above baseline.

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 states specific verb ('capture') and resource ('current session context') and target location ('.rekindle/captures/'). Clearly distinguishes from siblings like list_captures and read_capture, as this is the creation tool.

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 when to use: 'before a complex operation, when context feels at risk, or when the user requests it.' Also contrasts with automatic PreCompact hook. Lacks explicit 'when not to use' but positive guidance is strong.

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