List Page Templates

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description earns credit beyond that by disclosing the Cloud-only availability constraint and clarifying that responses omit the template body — both are behavioral facts an agent would otherwise learn only by failing or over-fetching.

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?

Three short sentences, front-loaded with purpose, then environment constraint, then return scope and the alternative. No redundancy and nothing that could be trimmed without losing routing information.

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?

An output schema exists, so return values need no further explanation; the description still summarizes the payload shape at a high level. For a two-optional-parameter read-only list tool, the Cloud-only note and the sibling hand-off cover everything an agent needs to invoke it correctly.

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% and both parameters (limit, space_key) are fully documented in the schema, including the global-vs-space default behavior. The description adds no additional parameter semantics, so the baseline 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?

States a specific verb and resource ('List Confluence page content templates') and immediately scopes what is returned (metadata only, not the body). It explicitly names the sibling tool confluence_get_page_template as the one that fetches bodies, so the agent can separate the two without opening either schema.

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?

Gives a clear routing rule: use this for metadata listings, use confluence_get_page_template when the body is needed. It also adds an environment constraint (Cloud only), which prevents wasted calls. It stops short of saying when to prefer this over a general confluence_search, so not a full 5.

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