swapcard_get_event

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

No annotations are provided, so the description must disclose behavioral traits. It neither states that the operation is read-only nor covers error handling, authentication, or side effects. Although 'get' suggests non-destructive behavior, the description does not add any transparency beyond the operation 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, concise sentence that leads with the action and resource, then lists the returned fields. It contains no redundant information and is well-front-loaded.

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 get-by-ID tool with one parameter and no output schema, the description sufficiently outlines what fields will be returned. It does not cover error cases or explicitly state that the returned object is complete, but given the low complexity, it is nearly complete.

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?

The schema provides full coverage for the only parameter (eventId) with a description 'The event ID'. The description's phrase 'by ID' adds no new meaning beyond the schema. Since schema coverage is 100%, the baseline of 3 applies; no additional parameter details are offered.

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 'Get a single Swapcard event by ID', specifying the verb, resource, and identifier. It also enumerates expected fields (title, dates, description, address, groups, community, stats), distinguishing it from sibling tool swapcard_get_events which lists multiple events.

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?

Usage is implied: the description indicates this retrieves a single event when an ID is available. However, it does not explicitly contrast with swapcard_get_events or mention when not to use it, so guidance is only implicit.

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