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, irreversible operation, but it doesn't specify consequences (e.g., data loss, recovery options), permissions required, or error handling. This is a significant gap for a mutation tool with zero annotation coverage.

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 with just three words, front-loading the core action. There's no wasted language or redundancy, making it efficient for quick comprehension, though this conciseness comes at the cost of detail.

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 complexity (a destructive delete operation), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address critical aspects like return values, error cases, or behavioral nuances, leaving the agent under-informed for safe and effective 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%, and the description adds no information about the 'meetingId' parameter beyond what the schema implies. It doesn't explain what a meetingId is, how to obtain it, or format requirements (e.g., UUID, numeric ID). With low coverage, the description fails to compensate for the lack of schema details.

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 ('a meeting'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'meetings_batch_archive' or 'meetings_update', which could also modify meeting states, so it doesn't reach the highest score.

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 like 'meetings_archive' or 'meetings_batch_archive' (which are present in sibling tools). There's no mention of prerequisites, permissions, or specific contexts for deletion versus archiving, leaving the agent with insufficient usage direction.

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