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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the write profile is known. The description adds meaningful behavioral context beyond that: debriefs accumulate and nothing is overwritten, which clarifies the append semantics that idempotentHint=false alone would leave ambiguous.

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?

Front-loads the action and resource, then the content categories, then the timing instruction. No filler sentences; every clause carries selection or invocation value.

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, trigger, and accumulation semantics for a mutation tool with six parameters and no output schema. It doesn't state what the call returns or how the appended debrief is identified, a minor gap rather than a blocking one.

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%, so the baseline is 3. The description's content list (how it went, what worked, what to improve, follow-ups) loosely maps to notes/went_well/to_improve/follow_ups, but adds no format, syntax, or rating guidance beyond the 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?

Specific verb (save) + resource (debrief onto a session in Metodic) with a content breakdown (how it went, what worked, what to improve, follow-ups). No sibling tool covers debriefs, so this is clearly distinguishable from the session-design/generation siblings.

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?

Gives explicit trigger conditions: after the user has run their workshop and reported back, or after a debrief conversation, with a sequencing instruction ('synthesize first, then save'). No when-not guidance or named alternative, but no obvious alternative exists among the siblings.

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