mind_quarantine

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

With no annotations, the description carries the full burden and delivers: it states expire 'only ever touches quarantined points, never live memory, and stays recoverable from the audit log', and that list is newest-first while show returns full content plus gate reason. It stops short of describing return shape or limits beyond the schema defaults, so not a full 5.

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 overall purpose, then breaks out each action in a tight parenthetical series with zero filler. Dense but well-ordered, every clause earns its place.

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?

No output schema and no annotations, yet the description covers the action set, id requirements per action, ordering, scoping, recoverability, and the safety boundary against live memory. Nothing an agent needs to invoke it correctly is missing.

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, but the description adds real meaning to the action enum the schema only labels 'What to do' – defining list vs show vs promote vs expire behavior and when id is needed. It exceeds the baseline without fully re-specifying every param.

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?

States a specific verb set (inspect, promote, expire) and a precise resource (entries the relevance gate filtered into the quarantine layer). It even names the three siblings it replaces (mind_quarantine_list / _show / _promote), so an agent can route to it without opening any schema.

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 maps each action to its intent: promote when 'the gate was too strict', expire when 'the gate was right', list for newest-first browsing with an optional library filter. The alternative-condition reasoning leaves nothing to inference.

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