palinode_session_end

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

Description adds context beyond annotations: it writes to daily notes and appends to project files, indicating write behavior but non-destructive. Annotations show readOnlyHint=false and destructiveHint=false, consistent with description. 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 concise sentences: first states purpose, second instructs on input. No redundant words, front-loaded with key 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?

Adequately covers input expectations and overall effect. Lacks explicit mention of session termination or return value, but output schema absent. Good for a write-oriented tool with 6 parameters.

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 mentions providing summary, decisions, and blockers, which matches parameters, but adds no new meaning beyond schema descriptions. Auto-detection details already in schema.

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 tool captures session outcomes to persistent memory, writes to daily notes, and appends to project files. It distinguishes from sibling tools like palinode_session_init by specifying 'end of session'.

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 'Call at the end of a coding or chat session', providing clear context. Does not explicitly mention alternatives or when not to use, but the context is strong enough given sibling palinode_session_init.

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