List Available Events

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

Since no annotations are provided, the description carries the full burden. It implies a read-only list operation, but does not explicitly state it is non-destructive, nor mention permissions or any behavioral traits. 'Lists' is clear enough for a simple retrieval, but lacks explicit confirmation of safety.

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 extremely concise: one short sentence directly stating the tool's purpose. No wasted words, front-loaded with meaning.

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?

Given no output schema and no annotations, the description is minimal. It explains what the tool does but does not describe the output format, any limitations, or how the returned events are structured. For a simple list tool, this may suffice, but it could provide more context.

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?

The input schema has no parameters, so no parameter details are needed. The description does not need to add meaning beyond the schema, which is already complete. Baseline for 0 parameters is 4.

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 clearly states it lists native events (POST_EVENT) available in triggers and procedures. It differentiates from sibling tools like list-triggers or list-procedures by specifying events rather than objects, but could be more explicit about what 'events' mean in the database context.

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 on when to use this tool vs alternatives such as subscribe_to_event or list-triggers. The description does not provide context for appropriate usage or exclude cases.

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