slack_delete_message

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

No annotations are present, so the description must disclose behavioral traits. It only mentions routing through an API endpoint with authentication scope, but fails to describe effects such as message irreversibility, notifications, or permissions required.

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?

While brief, the description sacrifices necessary detail. The routing and generic argument lines add minimal value and do not compensate for missing actionable content. This is under-specification, not effective 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?

Given zero annotations, no parameter documentation, and the presence of an output schema (unavailable here), the description fails to provide adequate context for a deletion tool. Critical information about required arguments, behavior, and return values is missing.

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 single parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds no meaningful semantics beyond the schema's type definition. The expected structure (e.g., required fields like channel and timestamp) is absent.

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 references 'delete_message' and 'slack.delete_message', which implies message deletion, but it does not explicitly state the tool's action. The purpose is conveyed primarily through the name rather than the description, making it somewhat 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?

There is no guidance on when to use this tool versus alternatives like slack_delete_canvas or slack_update_message. No prerequisites or context for invocation are provided, leaving the agent without decision support.

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