forget

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

With no annotations provided, the description carries the full burden. It clearly discloses the destructive effect ('Drop'), the target ('review history'), and the side effect ('freeing its id for reuse'). It does not mention irreversibility or error behavior, but the core behavior is transparent and specific.

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?

A single, front-loaded sentence with no filler. Every word contributes meaning, and the most important action ('Drop') comes first.

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 one-parameter tool with no output schema, the description states the operation, the constraint (finished session), and the outcome (id reuse). It could have pointed to sessions for finding sessionId or to abort for running sessions, but nothing critical is missing for selecting and invoking the tool.

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 schema gives no description for sessionId, so the description adds meaning by tying it to a finished session's id and explaining the reuse consequence. It does not explicitly name the parameter or explain where to find sessionId, but the parameter name plus the description make the intent clear.

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 states a specific verb ('Drop') and resource ('finished session from the review history'), and clarifies the consequence ('freeing its id for reuse'). It also distinguishes itself from abort by specifying the session must be finished.

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 implies this is for finished sessions only, which separates it from running-session tools like abort. However, it never explicitly names an alternative or states when not to use this tool, leaving some routing inferred rather than stated.

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