getWikiPages

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

With no annotations and a minimal description, no behavioral traits are disclosed. The tool likely fetches multiple pages, but it does not mention pagination, ordering, or any side effects. This is insufficient for an AI agent to infer safe usage.

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 extremely brief (3 words), which is under-specified for a tool with nested required parameters. It sacrifices informativeness for brevity, making it harder for the agent to understand the tool's purpose and usage.

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 complexity (nested required parameters, no output schema, many siblings), the description is completely inadequate. It fails to provide necessary context about how to invoke the tool and what to expect in return.

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 coverage is 0%, and the description adds no meaning to the parameters (pathParams with format and projectId). The agent cannot infer what 'format' or 'projectId' mean or how to use them without additional information.

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 'List wiki pages' clearly states the verb and resource, but it does not distinguish this tool from siblings like 'getWikiPage' (single page) or 'getWikiPageByVersion' (version-specific). More specificity (e.g., 'all wiki pages in a project') would help differentiate.

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?

No guidance is provided on when to use this tool vs. alternatives (e.g., getWikiPage, getWikiPageByVersion). Also missing context such as required projectId or format parameter.

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