List events

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it calls a GET endpoint, which is consistent and reinforces the non-destructive nature. No contradictions; the description provides minimal extra behavioral context 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?

The description is two sentences, focused and front-loaded with the action. However, the first sentence 'List events.' is slightly redundant with the second sentence. Could be more concise by combining them.

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 covers the basic purpose and endpoint but does not explain return values or pagination behavior (though pagination parameters are described in the schema). For a simple list tool, this is adequate but lacks full completeness given no output schema.

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 100%, so each parameter is already documented in the input schema. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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 that it lists events for a service, using the verb 'list' and specifying the resource ('events for the service with the provided ID'). It mentions the API endpoint. However, it does not explicitly distinguish from the sibling tool 'render_retrieve_event' which retrieves a single event, so it misses a slight differentiation opportunity.

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 implies usage when you need to list recent events for a service. There is no explicit guidance on when to use this tool versus alternatives like 'render_retrieve_event' or 'render_list_logs'. No exclusion criteria or prerequisites are mentioned.

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