delete_card

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

With no annotations, the description must fully disclose behavior. It states deletion is irreversible, but lacks details on required permissions, cascading effects (e.g., associated contents), or whether the card is permanently removed or moved to trash.

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?

Concise with clear purpose and warning. Front-loaded. Could be slightly more structured (e.g., separating behavior and params), but no wasted words.

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 destructive tool with an output schema, the description covers basics: action, warning, param, return. However, it lacks operational details like idempotency, error scenarios, or relationship to other card tools.

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 parameter 'card_id' is described as 'ID of the card to delete', which adds minimal value beyond the schema. Since schema description coverage is 0%, the description should clarify the parameter more, e.g., format or source.

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?

Clearly states the tool deletes a card (saved question). The verb 'delete' and resource 'card' are specific. Distinguishes from siblings like create_card, update_card.

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?

Includes a warning that the action cannot be undone, but provides no explicit guidance on when to use this tool versus alternatives like archive or soft-delete. No mention of prerequisites or context.

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