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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds value beyond them by disclosing the shape of the payload (per-group feature flags, auto-assignment ticket names, default group flag) and the underlying GET endpoint, which helps the agent reason about side-effect-free, cacheable reads. It says nothing about pagination limits or response size, which the schema partially covers via limit/offset.

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 sentences plus the endpoint, front-loaded with the returned resource content and followed by the actionable usage hint. The parenthetical feature list ('(agenda, questions, polling, networking, ratings, ...)') is slightly sprawling but earns its place by signalling the payload's variable-width nature rather than abstracting it away.

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 carries the burden of explaining return values and does so thoroughly (features, ticket mappings, default flag, ids). Since it is a simple 2-param read tool with full annotation coverage, the remaining gap — pagination/cursor behavior and whether results are event-scoped implicitly — is minor.

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% and both parameters (limit, offset) are documented in the schema, including the 'pass the previous reply's next_offset' convention, so the description properly defers to the schema. The description mentions 'ids' only in the context of output usage, adding nothing about limit/offset semantics. Baseline 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?

The description precisely enumerates what the resource contains (app features per group, ticket-name auto-assignment rules, the default group), which makes it clearly distinguishable from siblings like eventee_list_participants or eventee_list_partners. It lacks an explicit verb ('List...') and relies on the title/name for the action, but the noun phrase is specific enough that an agent knows exactly what it gets back.

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?

'Use the ids as group_id when inviting or registering people' explicitly ties this tool to the downstream invite/register flows (eventee_invite_attendees, eventee_register_people), giving real context for when to call it. There is no statement of when not to use it or of any prerequisites (e.g., event id / auth scoping), so it stops short of full routing guidance.

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