getWikiPage

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Show wiki page' only implies a read operation, but does not describe what data is returned, whether authentication is required, how parameters like format and include affect behavior, or any other side effects. This is almost no information beyond the obvious.

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 concise (3 words), but this is under-specification rather than good conciseness. It lacks structure and fails to convey essential information, making it more of a placeholder than a helpful description.

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?

The tool has a nested schema with required path parameters, an enum for response format, and an optional include parameter, but the description 'Show wiki page' is completely inadequate for guiding an agent to invoke it correctly. It does not mention the required parameters, the format selection, or the optional attachment inclusion, and it does not differentiate from sibling wiki tools.

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%, and the description adds no parameter meaning. It does not explain the purpose of pathParams (format, projectId, wikiPageTitle) or queryParams (include), leaving the agent to rely on parameter names alone. The description fails to compensate for the lack of schema descriptions.

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 'Show wiki page' uses a specific verb (show) and resource (wiki page), clearly indicating the tool retrieves a single wiki page. It is clear enough, but it does not explicitly distinguish from sibling tools like getWikiPages (list) or getWikiPageByVersion (specific version).

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 no guidance on when to use this tool versus alternatives. It does not mention that getWikiPages lists pages or that getWikiPageByVersion retrieves a specific version, leaving the agent without usage context.

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