Get Page Template

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

The readOnlyHint annotation already marks this as a safe read operation. The description adds context beyond that by specifying 'Cloud' scope and by clarifying that the returned body is in storage format, which is useful for an agent deciding if the output format matches its needs.

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 with no wasted words. It front-loads the action and resource, then delivers the key extra detail about the storage-format body 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?

For a one-parameter read-only tool with an output schema and a readOnlyHint annotation, the description covers what is needed: the resource, the identifier, the Cloud scope, and the body format. Nothing significant is missing for an agent to invoke this 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?

The schema has 100% description coverage for the only parameter, template_id, so the schema already explains that it is the ID of the template to retrieve. The description's 'by ID' phrase reinforces this but adds no further semantic detail, 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?

The description uses a specific verb 'Get' with a clear resource, 'Cloud page template by ID,' and adds the detail that the storage-format body is included. This distinguishes it from siblings like list_page_templates (listing) and get_page (regular pages rather than templates).

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 the usage: retrieve a Cloud page template when you have its ID. However, it does not explicitly state when to prefer this tool over alternatives, such as using list_page_templates to find a template ID or get_page for ordinary pages, nor does it offer any negative guidance.

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