passgage_delete_slack

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the delete operation and does not mention whether the delete is permanent, cascading, requires authentication, or returns any confirmation. This is a significant gap for a destructive action.

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 concise sentence that directly conveys the tool's purpose without any filler. It is appropriately minimal for a simple delete operation with one parameter.

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 mutation tool with no annotations and no output schema, the description should explain side effects, permissions, or expected response. It does none of these, leaving the agent to guess whether the delete is a hard or soft delete, if it succeeds silently, and what errors may occur.

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 fully documents the only parameter 'id' as 'The UUID of the slack to delete', giving 100% schema coverage. The description's 'by ID' merely restates this, adding no new meaning or context about the parameter's origin, format constraints, or usage nuances.

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 a slack by ID' clearly states a specific action (delete) on a specific resource (a slack) using a specific identifier (ID). This distinguishes it from sibling tools like create_slack, update_slack, and get_slack, making it unambiguous.

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 provides no guidance on when to use this tool vs alternatives, such as when to update rather than delete, or any prerequisites like required permissions. The usage is implied by the action but no explicit context, exclusions, or alternative references are given.

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