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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavior beyond that: results are newest-first, pagination is cursor-based ("page through"), and only a single event type is returned per call. It does not mention rate limits or the shape of a returned event.

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, front-loaded with the core action, with the event enumeration and the sibling redirect placed where they are most useful. Nothing is redundant.

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 agent gets no information about what an event record contains or that a pagination cursor is returned for the next call. Ordering and type scoping are covered, but the pagination contract on the response side is left implicit.

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 0%, so the description must carry the load. It explains the type parameter by naming all nine event values and frames project_id via "a project's events" and cursor via "page through," but it never mentions limit at all, leaving the page-size default and 200 maximum undocumented in prose.

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?

"Page through a project's events of one type, newest first" gives a specific verb, resource, scope, and ordering, and enumerates the exact event types. It explicitly distinguishes itself from get_send, which retrieves the full timeline for a single email.

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 names an alternative (get_send) and the condition that selects it: per-email history. It does not address when to prefer this over list_sends, which is the closest sibling for listing email sends, but the usage context it does provide is clear and actionable.

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