Supprimer une note de frais

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

Annotations already set destructiveHint: true and readOnlyHint: false. The description adds the explicit 'Action irréversible' warning, reinforcing the destructive nature. However, it does not disclose other behavioral details such as required permissions, cascading effects, or error handling.

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 extremely concise with a single line stating the action and a warning icon. It is front-loaded with the purpose and quickly conveys the irreversibility. No wasted words.

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?

Given the simplicity of the tool (delete by ID), the description covers the core functionality and irreversibility. However, it lacks information about the return value or confirmation of success, which would be helpful for agent decision-making. The absence of an output schema means the description should provide some behavioral cues, but it does not.

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 covers 100% of parameter descriptions, with the 'id' parameter clearly defined as 'Identifiant unique de l'entité BoondManager'. The description does not add any additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Supprime une note de frais' (delete an expense report) and identifies the resource and system (BoondManager). It effectively distinguishes from sibling tools like create, get, search, update by specifying the deletion nature.

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 does not provide any guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or scenarios where deletion is appropriate. The only hint is the irreversibility warning, but no explicit usage context.

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