promemoria_rimuovi

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It explicitly states that the tool removes an item, accepts a number or matching word, and that 'tutto' empties the entire list, which is an important destructive behavior. It does not discuss irreversibility or errors, but the core destructive semantics are transparent.

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 three short sentences with no filler. The main action is front-loaded, and the parameter behavior is explained immediately, making it easy for an agent to parse quickly.

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 single-parameter removal tool, the description covers the action, acceptable input forms, and the special 'tutto' command. The main gap is the absence of any return-value or error behavior, which matters somewhat because there is no output schema, but the agent still has enough to invoke the tool correctly.

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 has 0% description coverage, so the description must define the parameter. It explains that 'numero_o_testo' can be a list number, a word contained in the item, or the special sentinel 'tutto'. This adds significant meaning beyond the schema, though it could be even more precise about formats or edge cases.

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 uses a specific verb ('Toglie') and names the affected resource ('lista dei promemoria o della spesa'), clearly identifying it as a removal operation. It also differentiates from the sibling tools by describing the remove action rather than add or list behavior.

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 makes the use case clear: when you need to remove an item from a reminders or shopping list. It does not explicitly point to alternatives like promemoria_aggiungi or promemoria_elenco, but the context and sibling names are obvious enough that an agent can route correctly.

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