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

With no annotations, the description fully discloses behavior: soft-deletes (active=false), immediate effect on assessments, recoverable, operator-only requirement. Sufficiently transparent for a deletion-like operation.

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?

One concise paragraph with front-loaded purpose. No wasted words. Could benefit from clearer structuring (e.g., separating purpose, parameters, usage notes).

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 core purpose, effect, and usage hint. Lacks parameter description details and return value information (no output schema). Adequate but leaves the agent to infer parameter meaning from context.

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 0%, yet the description provides only implicit meaning for parameters (e.g., operator_key for authorization, signal_id for target, reason for justification). No explicit formats, constraints, or examples for any parameter.

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?

Explicitly states the action (UNLEARN a KB signal) with specific examples (rumored feature cancelled, signal no longer predictive). Clearly distinguishes from sibling tools like list_kb_signals by referencing it for ID retrieval.

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 usage context: signals that became false/obsolete. Notes operator-only restriction and points to list_kb_signals for finding IDs. Does not explicitly exclude other uses or name alternatives.

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