swapcard_import_sessions

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It only mentions create/update and supported features like formats and access control, but does not disclose idempotency, error handling, permissions, or rate limits. This is minimal for a mutation tool.

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 two sentences, direct and front-loaded with the core action. There is no filler or irrelevant information, making it appropriately concise.

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 the tool's complex nested schema, no annotations, and no output schema, the description is insufficient. It fails to explain the structure of the plannings array, expected return values, or operational constraints, making it hard for an agent to construct valid input or anticipate outcomes.

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 only vaguely references 'formats, video types, access control, and custom fields.' It does not map to specific parameters like eventId or plannings, nor explain the structure of the plannings array or required fields like clientId, beginsAt, etc. The description adds little value beyond what the schema already shows.

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 that it creates or updates sessions/plannings in bulk, using a specific verb (create/update) and resource (sessions/plannings). It distinguishes from sibling tools like swapcard_list_sessions or swapcard_delete_sessions by focusing on bulk mutation.

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 phrase 'in bulk' implies it is for batch operations, but there is no explicit guidance on when to use this tool versus alternatives like swapcard_import_event_people or swapcard_list_sessions. No exclusions or alternative mentions are provided.

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