swapcard_delete_custom_fields

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'Delete' and identifies what is removed, but does not mention permanence, cascading effects on existing field values, permission requirements, or possible failure modes. For a destructive tool this is a notable gap.

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 a single, front-loaded sentence with no unnecessary words or repetition. It earns its place by concisely conveying the core action and target resource.

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?

Given that there are no annotations, no output schema, and zero parameter descriptions, this one-sentence description is incomplete for a destructive multi-parameter tool. It lacks usage context, deletion consequences, and clear parameter role clarification.

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?

Schema description coverage is 0%, and the description does not explicitly explain eventId or fieldDefinitionIds. The phrase 'from an event' only weakly implies eventId; fieldDefinitionIds is not elaborated beyond the general word 'definitions.' The description does not compensate for the missing schema-level parameter documentation.

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: 'Delete custom field definitions from an event.' It identifies a specific resource (custom field definitions) and scope (event), which distinguishes it from siblings like swapcard_delete_event_people, swapcard_delete_event_documents, and CRUD custom-field tools.

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?

No guidance is given on when to use this tool versus alternatives, no prerequisites are mentioned, and no exclusions are stated. The description simply asserts the action without explaining when deletion is appropriate relative to update/create custom field tools.

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