List Page Templates

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

With readOnlyHint already annotated, the description adds useful behavior: Cloud-only availability and the fact it returns only metadata (ID, name, description, type) without the full body. This goes beyond the annotation without contradicting it.

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 sentences, each earning its place: the first states purpose, the second adds a key limitation, and the third points to the appropriate sibling for body retrieval. No fluff or 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?

For a simple list tool with two optional parameters, an output schema, and a read-only annotation, the description covers all necessary context: what it lists, the Cloud restriction, the metadata-only behavior, and the alternative for full content. The output schema handles return values, so no further detail is 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add additional parameter semantics beyond what the schema already provides; it simply mentions 'template metadata' which is already captured by the output schema.

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 'List' and the resource 'Confluence page content templates', and it distinguishes from siblings by noting it returns metadata without the full body. It explicitly names the alternative for body retrieval, resolving ambiguity.

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 provides clear context: it is Cloud-only and returns metadata only. It also gives an explicit alternative (use confluence_get_page_template for the body). However, it does not explicitly list when not to use this tool or other exclusions, so it falls short of a 5.

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