reflect_scars

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

No annotations, so full burden on description. Discloses character length minimums and that session_close uses reflections to determine execution_successful. Clearly describes input constraints and output consequences.

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?

Concise, front-loaded with purpose. Every sentence adds critical information (timing, outcome behavior, impact on session close). 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?

Fully explains the tool's role in the session flow, references related sibling (confirm_scars), and covers input constraints. No output schema, but describes usage outcome (sets execution_successful). Comprehensive for a reflection tool.

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 100%, but description adds value: evidence length minima (15/30 chars), explanation of outcome enum meanings, and that reflections are per surfaced scar. Goes beyond 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?

Clear verb+resource: 'scar reflection'. States it's the closing counterpart to confirm_scars, mirroring a protocol. Distinguishes its role in the session lifecycle.

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 instructs 'Call BEFORE session_close' and details behavior for OBEYED vs REFUTED. Mentions how session close uses reflections. Lacks explicit when-not-to-use but provides strong context.

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