swapcard_get_my_exhibitors

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds only an authentication-scope detail ('accessible to the authenticated Leads API token') but does not mention pagination behavior, ordering, result format, rate limits, or error conditions. This is minimal and leaves important behavior undisclosed.

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 filler or redundancy, making it efficient and front-loaded. The only issue is that it is under-specified, but that is penalized elsewhere; structurally it is 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?

The tool has no output schema, no annotations, and zero-parameter descriptions, yet the description offers only a one-line purpose. It does not explain the pagination parameters, the response shape, or how this tool relates to swapcard_list_exhibitors, so the context is far from complete for an agent to invoke it confidently.

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 compensate for the two parameters 'after' and 'first'. No meaning is added beyond the raw type information already in the schema; the likely pagination semantics of these parameters are left entirely undeclared.

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 a specific action ('Get the list of exhibitors') and a scope ('accessible to the authenticated Leads API token'). However, it does not explicitly differentiate this from the sibling tool swapcard_list_exhibitors, relying on the 'my' in the name and the token qualifier to imply the distinction.

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 about when to use this tool versus alternatives such as swapcard_list_exhibitors, nor are any prerequisites or exclusions mentioned. The token-scope hint is implicit but not actionable as usage guidance.

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