swapcard_delete_sessions

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

No annotations are provided, so the description carries full burden for behavioral transparency. It states the tool deletes sessions, which is obviously destructive, but it doesn't disclose whether the deletion is permanent, whether it requires specific permissions, or what happens if the provided IDs don't exist. This is a significant gap for a destructive action.

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 sentence that conveys the core purpose without any redundant phrases. It is front-loaded and economically expresses the tool's function, earning every word.

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 delete operation with only two parameters and no output schema, the description provides the basic purpose but lacks important context like irreversibility, required IDs format, or any note on error handling. It is adequate but leaves room for elaboration to fully prepare an agent for execution.

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 coverage is 0% and the description does not explicitly explain the parameters. It mentions 'by their IDs' and 'from an event', which hints that eventId corresponds to the event and planningsIds are the session identifiers, but it doesn't clarify that planningsIds is an array or provide any format details. The description adds only minimal meaning beyond the schema, insufficient to fully compensate for the lack of schema descriptions.

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), the resource (sessions/plannings), and the context (from an event by their IDs). It distinguishes from sibling tools like list_sessions and import_sessions by specifying deletion, making the purpose specific and 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 implies when to use the tool (when you want to delete sessions), but it doesn't explicitly contrast with alternative deletion tools like swapcard_delete_event_people or swapcard_delete_custom_fields, nor does it mention prerequisites such as needing the event ID and planning IDs from a prior list call. Usage guidance is minimal and mostly implicit.

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