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

With no annotations, the description carries the full burden of behavioral disclosure and falls short. It does not say whether results are paginated (though cursor param implies it), whether the list is sorted, whether it requires authentication, or what the volume of results typically looks like. 'Public' hints at accessibility but explicitly only as a data attribute, not a behavioral guarantee.

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 single sentence is concise and front-loaded, which is positive. But it is under-specified rather than genuinely concise – it omits critical information that a reader needs, so its brevity does not fully earn its place.

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 zero annotation coverage, 0% schema description coverage, no output schema, and two undocumented parameters, the description is inadequate. It does not describe pagination behavior, result shape, sorting, or access requirements, leaving significant gaps for an agent to fill by guesswork.

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%, so the schema does not explain limit or cursor at all. The description mentions nothing about these parameters, leaving an agent to guess that limit controls result count and cursor is an opaque pagination token. This is a clear gap that the description should have compensated for.

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 verb (List) and resource (public governance events), which is specific enough to be actionable. However, 'governance events' could overlap conceptually with siblings like list_challenges, list_karma_events, or get_constitution, and the description does nothing to differentiate itself from those.

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 is provided. The description does not explain when an agent should call this versus list_karma_events, get_constitution, or any other governance-adjacent sibling. The agent is left to infer usage entirely from the terse description.

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