meetings_delete

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete a meeting' implies a destructive operation, but it doesn't specify whether this is permanent or reversible, what permissions are required, whether it affects associated data, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects undocumented.

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 at just three words, with zero wasted language. It's front-loaded with the core action and resource. While this brevity contributes to under-specification in other dimensions, as pure conciseness it's optimal.

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, 0% schema coverage, and no output schema, the description is inadequate. It doesn't explain the deletion behavior, parameter requirements, error conditions, or what happens to related data. Given the complexity of a delete operation and the lack of structured documentation, this leaves too many gaps for reliable agent use.

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?

Schema description coverage is 0%, so the single parameter 'meetingId' is undocumented in the schema. The description provides no additional information about this parameter—no explanation of what format the ID should be, where to find it, or validation rules. With low coverage and no compensation in the description, this creates ambiguity for the agent.

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 meeting' clearly states the verb (delete) and resource (meeting), making the basic purpose understandable. However, it lacks specificity about what constitutes a 'meeting' in this context and doesn't distinguish this tool from potential alternatives like 'meetings_archive' or 'meetings_batch_archive' that appear in the sibling list.

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. With sibling tools like 'meetings_archive', 'meetings_batch_archive', and other meeting-related operations available, there's no indication whether this is for single meetings, permanent vs. soft deletion, or any prerequisites. The agent must infer usage from the name alone.

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