swapcard_list_exhibitors

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

Annotations are absent, so the description must carry the burden. It states 'List or search' but does not disclose behavior like pagination limits, sort capabilities, filtering semantics, or response format. No mention of read-only nature or complexity implications.

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, compact sentence with no filler. It is appropriately sized, but may be under-specified, leading to a trade-off between conciseness and completeness.

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 6 parameters, nested objects, no output schema, and no behavioral guidance, the description is significantly incomplete. It does not address pagination (after, first), sorting, filtering options, or what data is returned, making it inadequate for an agent to use correctly.

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 provides no explanation of any parameters. The schema itself has nested objects like sort, filter, and search, but the description does not clarify their meaning, usage, or relationships. This fails to 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 'List or search exhibitors in a community' clearly states the action (list/search) and the resource (exhibitors) with a community scope. It distinguishes from 'swapcard_get_my_exhibitors' and 'swapcard_upsert_exhibitors' by community context, but does not explicitly name alternatives or contrast with partner tools like 'swapcard_list_event_people'.

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?

There is no guidance on when to use this tool versus alternatives such as 'swapcard_get_my_exhibitors' or 'swapcard_list_event_people'. No mention of search vs filter usage, pagination needs, or when to prefer listing over other operations.

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