Prism MCP

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

With no annotations, description carries full burden and discloses: permanent deletion ('permanently deletes ledger entries'), default preservation ('Handoff state is preserved unless explicitly cleared'), safety requirements ('requires confirm_all=true'), and operational modes. Missing idempotency or error behavior details.

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?

Well-structured with front-loaded purpose, bulleted modes for scannability, and prominent warning emoji for destructive behavior. The brain metaphor adds slight length but serves an explanatory purpose. No redundant sentences.

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?

Comprehensive for a 6-parameter destructive tool without output schema. Covers all parameters via mode descriptions, safety constraints, and state preservation rules. Could improve by describing return value or success indicators.

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 has 100% coverage (baseline 3). Description adds semantic value by grouping parameters into logical 'Forget modes' (By project/category/age/Full reset) and clarifying interactions (confirm_all as safety flag for full reset, clear_handoff affecting preservation defaults).

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 opens with specific verb+resource ('forget (delete) accumulated knowledge entries') and distinguishes scope via 'session entries' vs 'handoff state'. The metaphor aids intuition without obscuring the technical function.

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?

Provides clear context for when to use ('remove outdated, incorrect, or irrelevant session entries to keep the knowledge base clean'). Distinguishes handoff preservation vs clearing, hinting at relationship with session_forget_memory. Lacks explicit 'when not to use' or named sibling alternatives.

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