fetchEventsPaginated

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

Discloses caching behavior, snapshot invalidation after ttl, and error condition ('Cursor has expired'). Annotations (readOnlyHint) are consistent, and description adds significant value beyond annotations.

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?

Well-structured with logical flow, but slightly verbose. Could be more concise while retaining clarity.

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?

Covers pagination and caching behavior, but lacks details on limit (page size?), filter criteria, and return structure. With 5 parameters and no output schema, the description is not fully complete.

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 40% with descriptions only for exchange and verbose. The description adds meaning to the cursor parameter (explains pagination flow) but does not address limit or filter semantics. Partial compensation for low schema coverage.

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?

Clearly identifies as a paginated variant of fetchEvents, describing the caching mechanism and cursor usage, distinguishing it from the non-paginated sibling.

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 clear guidance on first call (no cursor) vs subsequent calls (with cursor). Does not explicitly mention when not to use or alternatives, but the context implies using fetchEvents for non-paginated needs.

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