passgage_delete_user_shift

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states the destructive action ('Delete') but fails to mention irreversibility, cascading effects, permission requirements, or any return behavior. This is minimal transparency for a deletion tool.

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, clear sentence that efficiently conveys the essential action and target. It is well front-loaded and contains no unnecessary words, though it could include more context without significant cost.

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 simple delete tool with one well-documented parameter, the description is minimally viable. It covers the basic 'what' but lacks any behavioral caveats, usage context, or mention of side effects. Given the absence of annotations and output schema, more detail would improve completeness.

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 schema already thoroughly documents the single 'id' parameter with type and description (UUID). The description adds no extra meaning beyond confirming the deletion is by ID. Since schema coverage is 100%, the baseline of 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 specific action (Delete) and the exact resource (user_shift) along with the method (by ID), making the tool's purpose unambiguous. It distinguishes itself from sibling delete tools like delete_user or delete_shift by targeting the user_shift resource directly.

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 versus alternatives, no prerequisites, and no context about the deletion process. It only states what the tool does, leaving the agent with no situational cues for selection.

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