list_templates

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the operation is a read-only 'list,' and it discloses an error-related behavior: if the Design Manager API errors, the agent should copy the path from the HubSpot UI instead. It does not mention auth or rate limits, but the output schema covers return shape, so this is adequate.

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 compact and front-loaded: a one-line purpose, a short usage note, a fallback instruction, and a single parameter explanation. Every sentence adds value, with no repetition or filler.

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 one-parameter list tool with an output schema, the description covers everything an agent needs: what the tool returns conceptually, how to find the template_path, the parameter range, and what to do if the API errors. Nothing important 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?

The schema provides only the parameter name, type, and default, with 0% description coverage. The tool description compensates by explaining that `limit` sets the maximum results, constrains it to 1-100, and restates the default of 100. This gives the agent enough semantic detail to use the parameter correctly.

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 opens with a clear, specific statement: 'List CMS templates available in the portal.' It also explains the concrete purpose of the tool—to find the `template_path` needed by page and email create tools—which distinguishes it from sibling list tools like list_blogs or list_forms.

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 explicitly tells the agent when to use this tool: 'Use this to find the template_path that the page and email create tools need.' It also provides a fallback path if the Design Manager API errors. It does not explicitly contrast it with alternative list tools, but no sibling tool serves the same template-listing purpose.

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