forget

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adequately discloses the destructive nature ('Permanently delete') and the confirmation requirement ('nothing is deleted until the user approves'), which are key behavioral traits. It does not cover side effects or failure modes, but these are not critical for this simple tool.

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?

The description is two sentences long, front-loaded with the primary action, and each sentence adds essential information: the deletion action and the confirmation requirement. There is no redundancy or filler.

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?

For a simple one-parameter tool with an output schema, the description covers all essential aspects: what it does, what it accepts, and the critical confirmation flow. No missing information is needed for correct usage.

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?

The input schema only names the parameter 'item_ref' with no description, and schema coverage is 0%. The description compensates by explaining that the reference can be an id, URL, or title fragment, giving meaningful semantics beyond the schema. It could be more specific about the format of the id or fragment, but it provides sufficient guidance.

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?

The description clearly states the tool's action ('Permanently delete an item') and specifies the target resource ('by id, URL, or title fragment'). It is distinct from sibling tools like 'remember' and 'recall', establishing a unique purpose for deletion.

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?

The description provides clear context on when to use the tool (for deletion) and includes an important prerequisite (explicit user confirmation via MRTR elicitation flow). However, it does not explicitly mention alternatives or when not to use the tool, so it falls short of a 5.

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