Fetch Confluence page

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

Annotations already declare readOnlyHint=true, so the description is not burdened with stating it is read-only. It adds useful context about what data is retrieved (storage body, version data, ancestry), but does not disclose any additional behavioral traits such as pagination, error conditions, or authentication requirements.

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?

One concise sentence with no filler. It front-loads the core action and data scope. Every word is meaningful, and the description is appropriately brief for a straightforward fetch tool.

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 simplicity, one parameter, and the presence of an output schema (which should explain return values), the description is sufficient for understanding the tool's purpose. It could be slightly more explicit about when to use it versus search_confluence, but overall it provides a complete enough picture.

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?

The input schema has 100% description coverage for the single parameter (content_id), so the schema already fully explains the parameter. The description adds no additional parameter-level detail, which is acceptable given the schema's completeness.

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 specifies the action ('hydrate') and the resource (a Confluence page) with specific data components (storage body, version data, ancestry). This clearly distinguishes it from sibling search_confluence, which presumably locates pages rather than fetching full content.

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?

Usage is implied: the tool fetches a page's detailed data by content_id. However, there is no explicit guidance on when to use this instead of search_confluence, nor any mention of prerequisites or exclusions. The context of sibling tools exists but the description itself does not point to it.

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