plu_delete_message

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 behavioral disclosure. It merely states the action and mentions asking confirmation, but does not disclose whether deletion is permanent, reversible, requires specific permissions, or affects related data. This is insufficient for an agent to understand the tool's impact.

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 very short (two sentences), which achieves conciseness, but at the cost of missing essential details. The structure is acceptable but overly minimal for the information needed.

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 (one parameter, no output schema), the description should be sufficient but is not. It lacks explanation of what messageId represents, the result of deletion, and any side effects. The agent cannot fully understand the tool's usage context.

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?

With schema description coverage at 0%, the description must compensate but does not. The parameter messageId is not explained at all—no indication of its format, how to obtain it, or its significance. The agent has no semantic context beyond the schema's type definition.

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 verb and resource: 'Delete a message.' This distinguishes it from sibling tools like plu_delete_conversation (deletes conversation) and plu_send_message (sends message). However, it does not specify that the message is identified by messageId, which is slightly vague.

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 only usage guidance is 'IMPORTANT: ask user confirmation,' which is a mandatory instruction but does not provide context on when to use this tool versus alternatives like plu_delete_conversation or plu_delete_availability. No explicit when-to-use or when-not-to-use information.

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