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

There are no annotations, so the description must carry the behavioral burden. It does disclose that the operation lists published items from a static corpus, implying a safe, read-only action, and it lists the returned fields. However, it does not mention ordering, default pagination behavior, or whether full answer content is excluded, leaving some behavioral ambiguity.

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 with no redundant wording. The core action and resource are front-loaded, and the second sentence efficiently enumerates the returned fields. Every word earns 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 simple list operation with fully documented optional pagination parameters and an output schema, the description is largely complete. It states the source corpus, the published scoping, and the return fields. Minor missing details like default ordering or a maximum limit are not critical given the tool's simplicity and schema coverage.

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?

The input schema already describes both parameters clearly: limit is the maximum summaries to return and offset is the number to skip. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies given 100% schema coverage.

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 identifies a specific action ('List'), a precise resource ('published CanonicAI answer summaries from the static Answers corpus'), and the return fields. The verb 'List' and the scope of enumerating the corpus clearly differentiate it from the sibling tools get_answer and search_answers.

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 gives no explicit guidance on when to use this tool instead of get_answer or search_answers. It implies a paginated listing use case through 'List' and the limit/offset parameters, but it never states exclusions or directs the agent to alternative tools for single-item or search use cases.

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