invariance_session_record_summary_to_kb

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

Annotations already indicate a non-read-only, non-destructive write. The description adds concrete behavioral context: it creates a durable, searchable KB page under 'sessions/<session_id>' by default, clarifying what the side effect actually produces.

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 with no filler: purpose first, then usage timing, then default path. Every sentence earns its place and the most important information is front-loaded.

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?

For a simple write/persist tool, the description together with full schema coverage and annotations gives an agent everything needed: what it does, when to use it, where it writes, and why the output is valuable. No return format is necessary.

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 description coverage is 100% for all 5 parameters, so the baseline is 3. The description only restates the default path already present in the schema and adds no additional meaning about body, title, summary, or session_id.

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 action ('Persist a summary of an agent-session as a knowledge-base page') with a clear resource and purpose. It explicitly contrasts with the raw session timeline, making it easy to distinguish from session-logging and other KB tools.

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 explicitly specifies when to use the tool: at the END of a Claude Code task, after a meeting wraps, or after a screen-recording is reviewed. It provides clear temporal context, though it doesn't name alternatives or when-not-to-use scenarios.

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