List Page Templates

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

Annotations already declare readOnlyHint=true, and the description adds useful context beyond that: Cloud-only availability and the fact that responses include metadata but not the full body. This gives the agent a clear expectation of the operation's scope without contradicting the annotation.

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 three short sentences with no filler. The purpose is front-loaded, followed by the Cloud restriction, return scope, and a sibling pointer—each sentence earns its place.

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?

For a read-only list operation with an output schema, two well-documented optional parameters, and a clear sibling pointer, the description covers the essential invocation context. The Cloud-only caveat and metadata-only return behavior are both included, so nothing significant is missing.

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 both limit and space_key clearly documented in the input schema. The description does not add parameter-specific meaning beyond what the schema provides, 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 opens with a specific verb-resource pair, 'List Confluence page content templates', and clarifies that it returns metadata (ID, name, description, type) without the body. This distinguishes it from sibling tools like confluence_get_page_template, which fetches a template's full body.

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 points to an alternative: 'Use confluence_get_page_template to fetch a template's body.' It also sets a clear prerequisite by noting the operation is only available for Confluence Cloud, so agents know when this tool is applicable and when to route to a sibling.

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