events.list

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet provides zero information about pagination behavior, sorting criteria (despite 'ascending' parameter), rate limits, or data retention. It does not indicate whether results are real-time or cached.

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?

While brief (3 words), this is under-specification rather than effective conciseness. The single sentence fails to earn its place by providing insufficient information for an agent to correctly invoke a tool with 3 parameters and pagination logic.

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 list operation with 3 parameters (including pagination and filtering), zero annotation coverage, and no output schema, the description is grossly inadequate. It lacks filtering logic explanation, pagination model details, and return value expectations.

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%, requiring the description to compensate for undocumented parameters. The description mentions nothing about the 'accountId' filter, 'limit' pagination, or 'ascending' sort order, leaving critical parameter semantics entirely undefined.

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 'List Ryft events.' is essentially a tautology restating the tool name (events.list). While it identifies the domain ('Ryft'), it fails to distinguish this tool from sibling 'events.get' and provides no scope clarification (e.g., whether this returns all events or requires filtering).

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?

No guidance provided on when to use this tool versus the sibling 'events.get' or other related tools. There are no prerequisites, filtering recommendations, or warnings about the unfiltered nature of the list operation.

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