Get Page Views

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

The readOnlyHint annotation already signals a safe read operation, and the description adds the Cloud-only availability note. It does not describe any quirks of the analytics data, such as aggregation period or permission requirements, but for a read-only analytics tool this is acceptable.

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 concise and front-loaded with the core purpose, followed by a relevant availability note. Every sentence earns its place, and there is no fluff.

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 is simple, has a complete input schema, and an output schema exists, so the description does not need to explain return values. The Cloud-only note is the key missing context and is provided. Minor gaps like exact view-count semantics are not critical given the output schema.

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 100%, with page_id fully explained via a concrete URL example and include_title having a clear default and description. The tool description adds no parameter-specific nuance, so the baseline of 3 applies.

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 states the specific action ('Get view statistics') and resource ('Confluence page'), making it clear what the tool does. It does not explicitly differentiate from siblings like confluence_get_page or confluence_get_page_history, but the focus on view statistics is distinctive enough.

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 explicitly notes that the tool is only available for Confluence Cloud and not for Server/Data Center instances, giving clear when-not-to-use guidance. It does not name alternative tools for on-premise instances, but the platform limitation is directly useful for tool selection.

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