delete_calendar_service

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 explicitly labels the operation as a mutation ('[mutation]') and highlights the need for confirmation, indicating destructive behavior. While it lacks details on side effects or permissions, it adequately warns of the action's nature.

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: a single sentence with a clarification in parentheses. It conveys essential information without unnecessary words, earning its place efficiently.

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 the tool's simplicity (2 parameters, no nested objects, no output schema), the description is largely complete. It covers purpose, mutation flag, and confirmation requirement. It could mention permanence but is sufficient for correct invocation.

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 covers both parameters with descriptions (100% coverage). The tool's description reiterates the confirmation flag but does not add significant new semantic meaning beyond what the schema already provides. The mutation label is the main addition.

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 ('Eliminar servicio de calendario') and specifies the resource ('servicio/tipo de cita del calendario'). It distinguishes from sibling tools like update_calendar_service or create_calendar_service by indicating it's a deletion operation.

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 includes a confirmation requirement ('requiere confirmación: pasar confirm=true para ejecutar'), guiding the agent on a necessary step. However, it does not provide explicit when-not-to-use instructions or alternatives, but the context is clear.

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