delete_business_messages

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

The annotations already indicate destructive behavior (destructiveHint: true), and the description's 'Delete' matches this without contradiction. However, the description adds no additional behavioral context such as permanence, permissions, or effects on the sender/receiver, offering minimal value beyond the annotations.

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 a single, short sentence with no extraneous words, making it highly concise and front-loaded. It earns its place by stating the core action, though it could be expanded with more context without compromising structure.

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 destructive multi-parameter tool with no output schema, the description is too sparse. It lacks information about the expected return value, the need for a valid business connection, and any side effects or limitations of deleting business messages, leaving significant gaps.

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 0% schema description coverage and no parameter explanations in the description, the agent must rely on the parameter names alone. The description does not clarify what business_connection_id represents or how message_ids should be formatted beyond the schema's type definitions.

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 'Delete business messages' clearly states a specific action (delete) and a specific resource (business messages), distinguishing it from regular message deletion tools and read_business_message. Despite its brevity, it conveys the core function precisely.

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 delete_message or delete_messages. The description doesn't mention the business connection context or any prerequisites, leaving the agent to infer usage.

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