delete_message

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

With no annotations present, the description bears full responsibility for behavioral disclosure. It reveals that deletion involves 'two phases' but leaves the implications unexplained, and it omits important details about side effects or preconditions. This is a partial disclosure that creates more questions than answers.

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 exceptionally concise, front-loading the core action and a hint of complexity ('due fasi'). While short, it does not waste words; however, the 'two phases' note could be expanded without losing conciseness.

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 tool with four parameters, no output schema, and a hinted multi-step behavior, the description is critically incomplete. It does not explain parameters, the two-phase process, or any usage context, making it inadequate for an agent to use correctly without external knowledge.

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 description provides no information about the four parameters (message_id, folder, account_id, request_id), and schema coverage is 0%. Since the description does not compensate for the lack of parameter documentation, the tool fails to aid the agent in understanding parameter usage.

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 action ('Elimina' – delete) and the resource ('un messaggio' – a message), which is specific and distinct from sibling tools like delete_folder. However, it omits details about the 'two phases' aspect that could enhance clarity.

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?

No guidance is provided on when to use this tool versus alternatives like move_message or delete_folder. The 'two phases' hint implies a workflow but does not explain or exclude any use cases, offering no practical direction.

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