appointments_delete_type

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

With no annotations, the description must convey behavioral traits. It states the operation is destructive ('DELETE') and requires user confirmation, which is key. However, it omits details about irreversibility, effects on related data, or any 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?

The description is extremely concise—two short sentences that front-load the verb and resource. Every word serves a purpose, avoiding redundancy or filler.

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 operation with two required parameters and no output schema, the description is minimally complete. It identifies the action and a critical constraint (confirmation), but lacks context about prerequisites, side effects, or how it fits among siblings like appointments tools.

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 provides complete descriptions for both parameters ('id' as 'Appointment type ID' and 'confirmed' as 'Must be true'), covering 100% of schema fields. The description adds no further meaning beyond what the schema provides.

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 verb 'DELETE' and the resource 'appointment type', making the tool's purpose explicit. It distinguishes itself from sibling tools like 'appointments_delete' (which deletes appointments, not types) through the name and resource.

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, such as when to delete an appointment type versus other deletion operations. The description only mentions a confirmation requirement, which is a constraint rather than usage advice.

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