confluence_get_page_versions

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

The description adds no behavioral context beyond what the annotations already provide. While annotations correctly mark the tool as read-only, the description omits details about pagination, version ordering, or what constitutes a 'version', leaving the agent to guess the exact behavior.

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 with a single clear sentence. It is front-loaded with the key action and resource. However, it is so minimal that it sacrifices detail, which might hinder an agent's understanding, but it does not contain any wasted words.

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?

Although the tool is simple and has no output schema, the description fails to explain what 'version history' includes (e.g., version numbers, dates, authors). The agent has no information about the return format, which is essential for correct invocation and interpretation.

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 100%, so the baseline is 3. The description does not provide any additional meaning for the parameters beyond the schema, which already adequately describes 'pageId' and 'limit'.

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 'Get' and the resource 'version history of a page', making the tool's purpose unambiguous. However, it does not explicitly differentiate from the sibling tool 'confluence_get_page_version', which could cause confusion for an AI agent selecting between them.

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 usage guidelines are provided. The description does not indicate when to use this tool vs. alternatives, nor does it mention any prerequisites or context for invocation.

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