Get Events

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

With no annotations, the description carries the full behavioral burden. It conveys that the operation is a read of event results and gives the endpoint, but omits relevant behavior such as authentication needs, pagination behavior, RSID lifetime, or output format expectations.

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 a single focused sentence with no wasted words and puts the core purpose and resource up front. It is appropriately sized for a short definition, though its brevity contributes to gaps in other dimensions.

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 tool with five parameters, no annotations, no output schema, and 0% schema description coverage, this description is too sparse. It states the basic retrieval purpose but omits enough parameter, pagination, and behavioral context that an agent cannot confidently invoke it in complex cases.

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 compensate for all parameter meaning. It clarifies only the rsid parameter as 'previously-created' but says nothing about page, format, account, or columns, leaving four of five parameters semantically undocumented.

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 names a specific verb ('Retrieves') and resource ('event results'), and identifies the endpoint '/apiv2/events' and required input ('previously-created RSID'). It is clear what the tool does, but it does not distinguish itself from sibling tools like search_and_get_events or iterate_events_page.

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 phrase 'previously-created RSID' implies a prerequisite, but the description gives no explicit when-to-use guidance, no when-not-to-use conditions, and does not name alternatives. An agent would have to infer that this is the RSID-based retrieval path versus other event-fetching siblings.

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