meetings_delete_user_provider_link

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

With no annotations, the description discloses that deletion is immediate and irreversible, and that re-linking is required. It does not mention permission requirements or potential side effects, but for a simple link deletion, the transparency is good.

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 well-structured with clear sections (Required fields, Workflow tips, Common use cases). It is concise but could be slightly tighter; however, it efficiently conveys all necessary information.

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 single-parameter tool with no output schema, the description covers purpose, required field, usage tips, irreversibility, and re-linking. It provides an example UUID, making it complete and actionable.

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 the 'id' parameter 100%. The description adds meaning by specifying it is a UUID and that it matches the user_provider_id used when creating the link, which provides useful context beyond the schema.

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 tool deletes a link between a user and a video call integration, using specific verbs and resources. It distinguishes itself from the sibling tool 'meetings_link_user_provider' by being the inverse 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 provides explicit workflow tips (e.g., when to use, ID same as creation, immediate/irreversible) and common use cases. It lacks explicit guidance on when not to use, but the context is clear enough.

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