vizcharter_templates

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

No annotations are present, so the description carries the behavioral burden. It makes clear this is a read-only listing action by saying 'List', and adds useful behavioral context: the template computes layout/page size and layers can be added alongside. It does not document response shape details, but for a zero-parameter listing tool 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?

Compact and front-loaded. The first sentence states the action and outcome; the second adds essential usage context with a concrete spec example. Every sentence contributes, with no redundant 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 zero-parameter, no-output-schema listing tool, this is complete: it identifies what is returned, why it matters, and how to consume it inside the canvas spec family. An agent has enough information to invoke and apply the result 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 input schema has zero parameters, so there is nothing to document. Per the 0-parameter baseline, the description does not need to compensate for missing schema detail, and it already explains how the returned template/slot values fit into the canvas spec.

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 clear verb-resource pair: 'List the canvas poster templates with their slot schemas.' This distinguishes the resource from sibling tools like icons/themes/export, since it is specifically about canvas poster templates and their schema structure.

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?

Provides a concrete usage context: the templates are meant to be used with spec family 'canvas' and shows the expected spec shape. It does not explicitly contrast with sibling tools or say when not to use it, so it falls just 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.