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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description's 'Read-only' merely repeats it. The pagination/cursor behavior is disclosed, but that fact is also present in the schema, so added behavioral value is thin, though nothing is contradicted.

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?

One short, front-loaded sentence with no filler; the pagination/read-only facts come first. Minor jargon ('contract v0') adds no value, but there is no waste or reordering problem.

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?

With an output schema present, return values need no explanation, and annotations plus full schema coverage handle safety and parameters. What remains missing is differentiation from the search_answers sibling, which for a list tool is the one gap an agent would want closed.

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% for both parameters, so limit and cursor semantics are already fully documented. The description's mention of an 'opaque cursor' echoes the schema rather than extending it, making the baseline 3 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 states a verb (List) and resource (Answers), so the agent knows it enumerates answers. However, it largely restates the name/title and adds only 'paginated with an opaque cursor. Read-only,' leaving the boundary with the sibling search_answers implicit. Purpose is understandable but not sharpened against alternatives.

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?

There is no guidance on when to use this tool versus search_answers or get_answer, nor any stated prerequisites or exclusions. The reader can infer it enumerates the full set, but nothing in the text routes the agent.

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