memo_idle_capture

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

Description adds behavioral context beyond annotations: it is a write tool that saves to memo records, and dry_run prevents writing. No contradiction with annotations (destructiveHint=false, etc.). Minor gap: does not discuss rate limits or auth, but adequate given annotations.

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?

Efficient and front-loaded: first sentence states action and type ('Write tool'). Subsequent sentences provide usage guidance and dry_run behavior. No unnecessary information.

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, and parameter behavior. Assumes knowledge of 'idle capture' and 'session transcript', but context signals indicate siblings and annotations. Has output schema, so return values are covered. Minor gap: prerequisites like session existence are implied but not explicit.

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% with a brief description for dry_run. The tool description adds meaning by explaining the effect of dry_run in context ('no memories are written and the response only reports what would run'), which is more explicit than the schema's 'Preview what would be saved without writing anything.'

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 'Run idle capture... Extracts durable insights... saves as memo records.' It distinguishes itself as a write tool, contrasting with sibling read tools like memo_search and memo_ask.

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 ('after a meaningful unit of work, or periodically for clients without Stop hooks') and when not to use ('Do not use for normal lookup; call memo_search, memo_ask, or memo_unified_briefing'). Also explains dry_run mode.

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