Get Page Template

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

The annotations declare readOnlyHint=true, so the read-only nature is already covered. The description adds the detail that the body is in storage format, which provides some insight into the return content, but it does not disclose other behavioral aspects like authentication requirements or rate limits. This is consistent with the annotation, and the additional context is modest.

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 a single, clear sentence that immediately states the action and key detail about the body. It is front-loaded with the verb and resource, and every word earns its place without redundancy.

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, output schema present), the description fully covers the necessary context. It specifies the cloud variant and the body format, which is sufficient for an agent to invoke the tool correctly. No additional details are needed.

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 fully documents the single parameter `template_id` with a clear description. The tool description's mention of 'by ID' adds no semantic information beyond what the schema already provides. With 100% schema coverage, a baseline score of 3 is appropriate.

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', the resource 'Cloud page template', and the scope 'by ID', while also specifying that it includes the storage-format body. This distinguishes it from sibling tools like 'confluence_list_page_templates' and 'confluence_create_page_from_template' by focusing on retrieving a single template by its identifier.

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 implies when to use the tool: when you need a specific template by its ID and want its body content. It does not explicitly mention alternatives or exclusions, but the 'by ID' phrasing makes the use case clear enough without conflicting with listed sibling tools.

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