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

Annotations already establish read-only, non-destructive, open-world behavior, so the description adds real value beyond them: template events are filtered out, results are ordered (upcoming first) when the flag is set, and the return envelope is described field-by-field. It stops short of noting pagination semantics beyond what the schema says.

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?

Four short, dense sentences with the returned-field summary front-loaded and behavioral notes trailing. No filler, though the field enumeration is arguably redundant with the response and could be tighter.

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 five-optional-parameter read tool with full schema coverage and read-only annotations, the description covers return contents, default filtering (templates out), and ordering. Missing only an explicit note that results can be paged via next_offset and what an empty result means.

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 all five parameters are self-documenting; the description only touches `upcoming_only`, and its wording ('Upcoming events first when upcoming_only is set') blends ordering with filtering, which is slightly less precise than the schema's 'have not ended yet'. Baseline 3 applies since the schema does the heavy lifting.

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?

Implies a list operation over events and enumerates the fields returned (title, type, dates, active/public, max participants, summary), plus third-person specifics like template exclusion and 'APIv4 Event.get'. The verb is only implicit ('Events with ...') and relies on the tool name, but the resource and scope are unambiguous and no sibling tool targets events.

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?

The description gives conditional context for `upcoming_only` and states that template events are excluded, which is implied usage guidance. However, it never says when to pick this tool over e.g. civicrm_query or civicrm_list_entities for event data, nor any prerequisites (permissions, campaign/date scoping).

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