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

No annotations are provided, so the description carries the full burden; it does disclose the read-only, static-bundle nature of the data and enumerates returned fields. However, it says nothing about pagination behavior (limit/offset interaction), result ordering, or whether the list is complete or truncated, which matters for a listing tool.

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 sentences, front-loaded with the action and scope before the return payload. The return-field enumeration partially duplicates what the output schema already conveys, so it is not perfectly waste-free.

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?

Output schema exists, so return values need not be explained in depth, and the low-complexity read-only nature with two optional params means little else is required. A brief note on pagination or result ordering would close the remaining gap.

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?

Both parameters (limit, offset) are documented in the schema at 100% coverage, so the schema does the heavy lifting. The description adds no syntax, defaults, or pagination semantics beyond what the schema already states.

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 gives a specific verb ("List") and resource ("published CanonicAI domain canons") and names its data source ("static canon bundle"). The plural/collection framing distinguishes it from the singular sibling get_canon without needing to name it 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 enumeration nature of the tool, but there is no explicit when-to-use, when-not-to-use, or comparison against siblings like search_constructs or get_canon. An agent must infer that this is the browse-all entry point rather than a targeted lookup.

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