swapcard_list_sessions

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

No annotations exist, so the description carries the burden. It states the tool lists/searches sessions, indicating a read operation. However, it does not disclose pagination behavior, return format, or any constraints like rate limits, which an agent might need to know. It adds only slightly beyond the name.

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 with no fluff, front-loading the primary action. However, it could be slightly more structured to list parameters, but the brevity is acceptable for a simple listing tool.

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?

With no output schema, the description should clarify return values or pagination. It does neither. It also fails to describe the 'search' and pagination parameters, making the tool incomplete for an agent to use effectively. The 6 parameters and nested objects demand a more thorough explanation.

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% for parameters, so the description must compensate. It mentions filtering by event, format, and speaker, and sorting by various fields, but does not explain key parameters like 'search', 'after', 'first', or the full filter object. Many parameters (placeIds, clientIds) are omitted, leaving the agent to infer from names.

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 tool lists or searches sessions/plannings within a community, and explicitly mentions filtering by event, format, and speaker, as well as sorting. This distinguishes it from sibling tools like swapcard_list_meetings or swapcard_list_exhibitors, which target different entities.

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 purpose is unambiguous: use it to retrieve sessions. It implies filtering and sorting capabilities, which are also reflected in the schema. However, it does not explicitly state when not to use it or mention alternatives, though the context of 'sessions' separates it from peers.

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