wiki_list_pages

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

With no annotations provided, the description carries the full burden. It discloses the return format ('Returns a list of pages with id, path, title, description, tags, updated_at'), which is helpful. However, it lacks details on behavioral traits such as pagination, rate limits, permissions required, or error handling, leaving gaps for a tool with no annotation coverage.

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 front-loaded with the core purpose, followed by return details and a usage tip. Every sentence earns its place, with no wasted words, making it efficient and easy to parse for an AI agent.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, parameter semantics, and return format. However, it lacks some behavioral context (e.g., pagination or error handling), which would be beneficial despite the simplicity.

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 schema description coverage is 0%, so the description must compensate. It fully explains the single parameter ('path_prefix'), detailing its purpose ('filtered to those whose path starts with path_prefix'), default behavior ('Pass path_prefix='' to list all pages'), and effect. This adds significant meaning beyond the bare schema.

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 clearly states the verb ('List') and resource ('wiki pages'), specifying the optional filtering capability ('filtered to those whose path starts with path_prefix'). It distinguishes from siblings like wiki_search_pages by focusing on path-based filtering rather than general search.

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 provides clear context on when to use this tool ('optionally filtered to those whose path starts with path_prefix') and includes a usage tip ('Pass path_prefix='' to list all pages'). However, it does not explicitly mention when not to use it or name alternatives like wiki_search_pages for different filtering needs.

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