getWikiPageByVersion

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

With no annotations, the description must disclose behavioral traits but only says 'Show', implying a read operation without specifying return format, error behavior, or side effects. It does not clarify whether it returns content, metadata, or how version existence is handled.

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 one short, front-loaded sentence with no fluff, but it is under-specified. It omits essential details that are not recoverable from the schema, making it more terse than usefully concise.

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 nested pathParams/queryParams structure, six underlying parameters, and no output schema, the description is inadequately complete. It fails to explain parameter meanings, return values, or operational context, leaving agents to guess.

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 explanations. It hints at version-based lookup but does not clarify the meaning of format, include, projectId, or wikiPageTitle, leaving the agent without critical 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 clearly states a 'Show wiki page' operation with the qualifier 'by specific version', making it distinct from sibling tools like getWikiPage and getWikiPages. The verb and resource are specific, and the version qualifier differentiates the tool, though it does not explicitly name an alternative.

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 versus getWikiPage or how to list available versions. The description gives no context, exclusions, or alternatives, leaving the agent to infer usage solely from the name and schema.

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