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

Annotations already declare readOnlyHint and destructiveHint, but the description adds value by detailing the returned information (submitter, timestamp, payout flag, space conflicts) and explaining conflict types (hard/soft). The 'Read-only' tag reinforces the annotation.

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?

The description is well-structured with the main purpose first, then specific details, and ends with follow-up tools. Every sentence adds value, and the length is appropriate for the complexity.

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?

Given no output schema, the description explains the output fields (submitted, when, payout request, space conflicts) and behavior (first approval wins for soft conflicts, payout routing goes to studio). This is complete for the tool's context.

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?

The only parameter is community_id with 0% schema coverage. The description mentions it is required and implies it identifies the community you run. While not adding format constraints, the context is sufficient for a single, self-explanatory parameter.

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 uses a specific verb ('List') and resource ('pending community events'), clearly stating it returns who submitted, when, payout request, and space slot conflicts. It distinguishes from sibling tools like approve_community_event and reject_community_event, making the purpose unambiguous.

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?

Explicitly states when to use (list pending approval events) and provides follow-up actions: approve with approve_community_event or reject with reject_community_event, with a note about payout submissions. This gives clear context and alternatives.

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