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

Annotations already cover the safety profile, and the description adds context an agent could not infer: 50 results per page, the has_more/next_cursor paging loop, no billing, and a 60 calls-per-minute per-connection limit shared across all tools.

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?

A single dense paragraph, front-loaded with purpose and scope, followed by routing, pagination, and operational limits. Every sentence carries a distinct, non-redundant instruction.

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 field detail is unnecessary; the description still covers discovery purpose, sibling routing, pagination, billing, and rate limits. Nothing an agent needs to call this correctly 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?

With 100% schema coverage the baseline is 3, but the description adds the paging contract that the schema alone does not state: the default page size and the instruction to pass `next_cursor` as `cursor` while `has_more` is true. It also ties template `type` values to the correct downstream render tool, which is meaning beyond the enum itself.

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 the published templates of the connected workspace') and enumerates the fields returned (id, name, type, live version), which lets an agent distinguish it immediately from get_template_schema and the render_* siblings.

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 explicit when-to-use ('to find the `template_id` for a document the user describes'), an explicit when-not ('skip it when you already have the id'), and routes by template type: pdf_code/pdf_markdown to render_pdf_from_template, image_canvas to render_image_from_template, and schema lookup to get_template_schema.

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