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

With no annotations, the description carries the full behavioral burden, and it discloses only that results are scoped to the caller's own identity. Ordering, whether results are paginated, what an 'event' record contains, and any rate limits are all unstated.

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?

A single sentence with no filler, and the scope qualifier ('authenticated caller's') is front-loaded. It is efficient rather than padded, though it is arguably too terse to do its job.

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 tool with three undocumented parameters, no output schema, and no annotations, this leaves the agent without the pagination contract or the shape of returned events. The minimum needed to call it correctly is largely missing.

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?

All three parameters (type, limit, cursor) have 0% schema description coverage and the description explains none of them. That limit and cursor imply pagination and type implies a filter is left entirely for the agent to infer, matching the calibration case for three undocumented parameters.

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), resource (karma events), and scope (authenticated caller's), which is far clearer than the tautological alternative. It does not, however, contrast itself with siblings like get_karma or get_agent_karma, leaving the summary-vs-event-log distinction to inference.

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 when-to-use guidance and no mention of alternatives. An agent must guess whether this is a supplement to get_karma or a standalone audit trail, and no exclusions or prerequisites are given.

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