list_wiki_pages

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

With no annotations provided, the description carries the full burden but only restates the tool's purpose ('List every wiki page') without disclosing side effects, read-only guarantees, permissions, authentication needs, or error behavior. It does not add any behavioral context beyond what the name implies.

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 purpose sentence, followed by a compact args section. Every line is purposeful, and there is no redundant content.

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 tool with one parameter and an output schema, the description covers the basic operation and parameter, which is adequate for selection. However, it lacks notes on edge cases (e.g., empty project, invalid identifier) and does not explicitly state that this is a read-only operation, which would be helpful given no annotations exist.

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 has a single parameter with no description (0% coverage), so the description's 'project_identifier: project identifier (e.g. 'my-project')' provides essential meaning. It clarifies the parameter's purpose and gives a format example, though it doesn't specify whether the identifier is a slug, numeric ID, or full path.

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 the specific verb 'List' and resource 'every wiki page of a project', clearly distinguishing from sibling tools like get_wiki_page and delete_wiki_page. The phrase 'every' emphasizes the all-inclusive scope, leaving no ambiguity about the operation.

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 when you need all wiki pages for a given project_identifier, but it does not explicitly state when to prefer this over get_wiki_page or search, nor does it mention what not to use it for. The context is clear but lacks any exclusions or alternative tool references.

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