list_templates

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

No annotations are provided, so the description carries the full burden. It adds limited behavioral context by specifying 'all available' and 'with descriptions', but it does not mention ordering, permissions, error cases, or pagination. The behavior is simple but under-disclosed relative to the lack of annotations.

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 sentence that directly states the tool's function without any redundancy. It is appropriately minimal for a simple list operation.

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 tool with no parameters and no output schema, the description is mostly adequate, promising a list of templates with descriptions. However, it could be more explicit about the return structure or any limitations (e.g., whether archived templates are included), leaving a small gap in completeness.

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?

With zero parameters, the empty input schema fully covers parameter semantics. The description adds no parameter information, but none is needed, so the baseline of 4 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 clearly states the tool lists all available page templates and includes their descriptions, using a specific verb ('List') and resource ('page templates'). This makes the purpose unambiguous and distinct from siblings like create_page_from_template or get_page.

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 usage for retrieving available templates but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusion criteria. The context of sibling tools could suggest use cases, but the description itself does not articulate them.

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