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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds the underlying REST mapping, which is modestly useful context, but says nothing about paging behavior, result limits, or auth requirements beyond what the schema's top/skip already imply.

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?

Front-loaded with the purpose, then immediately the filter examples, then the endpoint. Compact with essentially no filler; only the endpoint mapping is arguably redundant, but it is cheap and informative.

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 say something about what is returned (a paged collection of event objects) or default paging behavior, and it does not. Six optional parameters are otherwise well covered by the schema, so this is adequate but not 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?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning by showing concrete $filter syntax ("IsUpcoming eq true", "Tags in [workshop]", "Id in [1,2]") that the schema merely gestures at with a field list. This is exactly the kind of syntactic detail an agent needs to build a valid filter.

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+resource ("List events") and pins it to the underlying endpoint GET /accounts/{accountId}/events, so the agent knows exactly what collection is returned. It does not, however, differentiate itself from close siblings like wildapricot_get_event or wildapricot_list_event_registrations, so there is no explicit sibling routing.

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 statement of when to use this tool versus get_event (single record) or list_event_registrations, and no guidance on paging strategy or when to prefer count/ids_only. The filter examples hint at usage patterns but are parameter syntax, not selection guidance.

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