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

Annotations already cover readOnly/idempotent, and the description adds behavior beyond them: results are ordered oldest-first, the host permission requirement, and the approvalMode discriminator with the consequence that approve_guest_request refuses 'order' entries.

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 what the tool returns, then the routing advice, then the approvalMode caveat. No filler sentences; each clause adds decision-relevant information.

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 compensates by describing the returned fields (count, requester, tier, timestamp) and ordering. Permissions, prerequisites, and the follow-up action path are all covered.

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 0% for the single event_id param, so the description carries the burden; it states event_id is required and that the caller must be a host, though it does not describe the id format or length constraints. Adequate compensation with a minor gap.

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 with scope: 'List the pending WAITLIST / approval requests on a live event you manage'. It disambiguates from neighbors like list_join_requests and list_guests by naming the waitlist/approval concept explicitly.

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?

Names the paired tools (approve_guest_request / deny_guest_request), states the prerequisite (event_id, must be a host), and routes the 'order' case away from approve_guest_request to Producer Studio. Explicit when/when-not guidance with an alternative.

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