Delete Meeting

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds redundant emphasis on permanence and irreversibility but does not disclose additional traits like side effects, rate limits, or prerequisites beyond what annotations provide.

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 relatively concise but contains redundancy, repeating 'This cannot be undone' twice. The inclusion of API version info is useful but not essential for an agent's invocation logic.

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 well-defined parameters and annotations, the description sufficiently covers core functionality and required parameters. It lacks details on return formats or error handling, but these are not critical given the tool's simplicity and no output schema.

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?

Input schema coverage is 100%, and the description only repeats the required parameters (project_id, id) already documented in the schema. No additional meaning or context is added beyond the schema definitions.

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 'Delete a specified meeting from the system' and emphasizes permanent removal. It specifies required parameters and API endpoint, distinguishing it from sibling tools like create_meeting_project or update_meeting_project.

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 states 'Use this to permanently delete' and notes it cannot be undone, providing basic guidance. However, it does not explicitly mention when not to use it or compare with alternatives, which would be helpful for an agent deciding between tools.

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