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

With no annotations, the description carries the full behavioral burden. It usefully discloses pagination via offset, limit range and default, and the return JSON shape, but it does not state permission/access scope, ordering, rate limits, or whether all accessible spaces are searched when 'space' is omitted.

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 short, front-loaded, and well-structured with Args and Returns sections. The return-shape line is somewhat redundant because an output schema already exists, but the parameter documentation is efficient and earns its space.

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 three-parameter listing tool with an output schema and no annotations, the description provides the key usage context, all parameter meanings, and pagination behavior. Minor omissions remain around access scope and result ordering, but nothing critical to invoking it correctly is 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?

Schema description coverage is 0%, so the description must compensate, and it documents all three parameters with useful meaning: space accepts a slug or name fragment, limit is constrained to 1-300 with default 100, and offset supports pagination. The offset explanation is minimal, but the definition fills the main schema gap.

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 and resource: 'List documented pages, optionally inside one space.' It also distinguishes the inventory-style use case from answer-seeking search with 'rather than an answer,' which separates it from search_docs and get_doc without requiring the sibling schemas to be opened.

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 clearly states when to use it: when the caller wants an inventory of manuals rather than an answer. It implies the alternative search behavior, but it does not explicitly name search_docs or give other exclusions, so it falls short of fully explicit alternative routing.

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