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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds that these are raw ingested events for metering plus the underlying endpoint, which is modest extra context; it says nothing about pagination behavior or result volume beyond what the schema already documents for page/limit.

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?

Two tight sentences with the core purpose front-loaded; the trailing endpoint reference (GET /v1/events/) is mildly redundant but harmless.

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 read-only list tool with fully documented parameters and no output schema, the description conveys what the records are and how they can be narrowed. It is adequate, though it stops short of describing the shape of a returned event or pagination 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 100%, so all 8 parameters are already documented. The description's filter list duplicates the schema fields without adding syntax, format, or interaction details, so the baseline 3 applies.

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?

States a specific verb (List) and resource (raw usage events ingested for metering) and enumerates the filter dimensions. The word 'raw' implicitly distinguishes it from aggregate siblings like polar_get_meter_quantities, but no sibling is named explicitly.

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?

Usage is implied by the filter list (customer, meter, name, time), so an agent can infer when this is appropriate, but there is no explicit when-to-use guidance and no exclusion pointing to the aggregation alternative (polar_get_meter_quantities) when summarized data is wanted.

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