calmesh_remove_connection

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It explicitly states the destructive nature (removes the connection and stops syncing) and the required scope ('full'). This is valuable context beyond what the name implies, though it does not mention reversibility or side effects on dependent data.

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 consists of three short sentences, each serving a distinct purpose: stating the action, explaining the behavioral effect, and specifying the permission requirement. There is no redundancy or unnecessary detail, and the purpose is front-loaded.

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 single-parameter removal tool with no output schema, the description adequately covers the core function, the consequence of the action, and the required scope. It provides sufficient context for an AI agent to select and invoke the tool correctly, without needing additional return value details.

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 input schema already provides a complete description of the single parameter: 'Connection ID to remove.' The description does not add any additional parameter-specific meaning, so the baseline score of 3 is appropriate given 100% schema coverage.

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 ('Remove') and the specific resource ('a calendar connection'). It further explains the consequence (disconnects the provider and stops syncing), which distinguishes it from sibling tools like list or start connections. The verb-object structure is unambiguous.

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 clear context that this tool removes an existing calendar connection, which implies when it should be used. However, it does not explicitly mention alternatives or state when not to use it. The effect description ('disconnects the provider and stops syncing') helps an agent decide, but there is no direct comparison to other connection-related tools.

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