List Wiki Pages

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

The description discloses the response envelope ({ items, pagination }), the pagination fields, and the default page_size of 30. This adds useful context beyond the readOnlyHint annotation, which only signals a safe read operation. No contradiction with annotations.

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 tight sentences that front-load the core action and follow with the response structure. No wasted words or redundant phrases.

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 4 well-documented parameters and a readOnlyHint, the description is fairly complete: it explains the response shape and pagination behavior. It could explicitly state that the project parameter is required to scope results, but the schema already marks it as required.

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%, so the baseline is 3. The description mentions 'optionally filtered by the given query parameters' but does not add meaning to individual parameters beyond what the schema already provides. The mention of default page_size restates the schema's own default.

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 uses a specific verb 'List' and names the resource 'wiki_pages', clearly distinguishing it from sibling tools like wiki_page_get or wiki_page_get_by_slug. It also mentions optional filtering and the response shape, making the tool's function unambiguous.

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 implies usage for listing pages with optional filters, but it does not explicitly contrast with alternatives like wiki_page_get_by_slug or wiki_page_get. There is no 'when not to use' guidance, though the title and sibling names make the purpose fairly clear.

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