event_list

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

The description starts with '[READ]' indicating a safe read operation, and explains that the result reports `returned`, `limit`, and `truncated` for transparent pagination. However, with no annotations, it could be more explicit about safety and side effects.

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 concise (5 lines), front-loaded with the summary, and every sentence adds value. No fluff.

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?

The description lists returned fields and pagination behavior, which is adequate for a simple list tool. However, it lacks sorting, filtering, or error handling details. Without an output schema, the description provides a good overview.

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%, but the description fully compensates by explaining the limit parameter's purpose, default, and result reporting, and the target parameter's meaning and default. This adds critical context beyond the schema.

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 explicitly states '[READ] List events' with specific fields (extId, title, creation time, source entity). This clearly defines the verb and resource, distinguishing it from sibling tools like snapshot_list or alert_list.

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 explains the parameters and their defaults, but lacks guidance on when to use event_list versus similar tools like audit_list or task_list. Usage context is implied but not explicit.

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