memory_guard_reclaim

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

Description discloses immediate vs queued behavior for peers, adding nuance. Annotations (destructiveHint=false) are not contradicted; unload is not necessarily destructive. Could mention side effects like potential performance impact.

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 clear sentences plus a focused parameter explanation. No fluff, front-loaded with purpose.

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?

With output schema existing, return values are covered. Description explains functionality and parameter. Could mention relationship to sibling memory guard tools for completeness.

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 0%, but description fully explains the 'scope' parameter with two options ('self' and 'all') and their effects, adding essential meaning 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?

Description clearly states 'Unload thread-keeper model/caches now', specifying the action and resource. It distinguishes from siblings like memory_guard_check and memory_guard_status which have different purposes.

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?

Describes when to use (immediate unload) and scope options, but does not explicitly mention when not to use or compare to alternative memory management tools.

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