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

Annotations declare readOnlyHint=true, so safety is already covered, and the description goes further by disclosing the concrete contents of the response (capacity, attending/waiting counts, registration and cancel deadlines) plus the backing endpoint GET /events/{id}. It does not describe handling for a missing/invalid id, but the content disclosure is genuinely additive.

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?

Two tightly packed sentences: the outcome and its payload come first, the API mapping last. Every clause carries information and nothing is repeated.

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 takes on the burden of telling the agent what comes back, and it does so concretely. It is nearly complete for a single-resource read; the only gap is not hinting at how expand/fields alter the payload shape, which the schema does cover.

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 100%, so event_id, expand, and fields are already fully documented with examples in the schema. The description only alludes to the id parameter and adds no syntax or format detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Fetch one class or appointment by id') and enumerates the returned data (capacity, attending/waiting counts, registration and late-cancel deadlines). This clearly separates it from the sibling goteamup_list_events, which returns many 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 only implied: 'by id' and 'one' suggest it is the single-record lookup counterpart to goteamup_list_events, but neither that sibling nor any when/when-not condition is named. No prerequisites (e.g. needing an id from a list call) are stated.

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