Delete iCal Feed

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

Beyond the annotations (e.g., destructiveHint=true), the description adds that imported dates are cleared, providing context on the effect. It also specifies the 'response_format' parameter and gives an example output format hint.

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 concise: two sentences, an args list, and an example. No redundant information. Front-loaded with key details.

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?

The description covers the basic operation and required parameters, but lacks details on error handling, idempotency behavior, or return structure (no output schema). Adequate for a simple delete tool but could be more complete.

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 description lists parameters with brief explanations and provides a concrete example with actual values, adding meaning beyond the input schema. Schema coverage is 100%, so baseline is 3, but the example elevates it.

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 an imported iCal feed' and its effect: 'Imported dates from this feed are cleared.' It uses specific verb and resource, and distinguishes from siblings like import and list feeds.

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 implies usage by providing an example ('Remove the Airbnb calendar connection'), but does not explicitly state when to use this tool versus alternatives or when not to use it. No mention of prerequisites or alternatives.

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