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

Annotations already establish readOnly/openWorld/no-destructive, so the bar is lower, yet the description adds real behavioral context: Guest Tags are only visible to hosts or co-hosts (a permission-gated field), and it requires a Cotlet API key with app access. These are non-obvious constraints beyond the structured fields.

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-loads the key idea, but the first sentence ("The Tracking page: each guest or group with status, number attending and Guest Tags") is essentially repeated verbatim in the second sentence, wasting space. The trailing API-key note is useful but the redundancy is avoidable.

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 read-only list tool with no output schema, the description covers the returned fields (status, attending count, Guest Tags), the permission caveat on Tags, and the auth prerequisite. Combined with the fully documented schema, an agent has enough to call it correctly; only cross-sibling routing is thin.

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?

With 100% schema description coverage, the schema already documents event_id, tag, search and status, so baseline is 3. The prose only reiterates the single-event scoping (event_id) and does not add filter syntax or interaction details beyond what the schema provides.

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 concrete verb and resource – returns the Tracking-page rows (each guest/group) for one event, including status, attending count and Guest Tags. It also names the sibling tools get_guest and tag_guests as follow-ups, aiding differentiation. It does not, however, distinguish itself from close siblings like export_guest_list or get_guest, so it stops short of a 5.

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?

Provides a follow-up chain ("Pass guest_id to get_guest or tag_guests") and implies usage is scoped to a single event's Tracking page. However, it never states when to prefer this over export_guest_list or other guest-listing siblings, leaving the primary routing decision to inference.

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