passgage_delete_shift_setting

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 does not mention that deletion is permanent, any side effects on related data, permission requirements, or error behavior if the ID doesn't exist. It only restates the operation without additional context.

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 that conveys the core purpose with no wasted words. It is appropriately front-loaded and easy to parse.

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 operation with no annotations and no output schema, the description is under-specified. It lacks warnings about irreversibility, potential dependencies, or expected return behavior. Although the tool is simple with only one parameter, the description does not provide sufficient context for an agent to fully understand the consequences.

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 already fully describes the 'id' parameter with 100% coverage, stating it is the UUID of the shift_setting to delete. The description adds no extra meaning beyond 'by ID', which is redundant with the schema. Baseline 3 applies due to high schema coverage.

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 action (delete), the resource (shift_setting), and the method (by ID). This distinguishes it from sibling tools like passgage_get_shift_setting, passgage_create_shift_setting, and passgage_update_shift_setting.

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 usage is implied by the tool name and simple sentence, but there is no explicit guidance on when to use this tool versus alternatives, such as updating instead of deleting, or any prerequisites like existing shift_setting IDs. No exclusions or alternative recommendations are provided.

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