strata_chart_templates

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

With no annotations, the description carries the full burden of behavioral disclosure. It signals a read-only listing operation and describes the output fields, which is useful, but it does not explicitly confirm that no side effects occur or describe any environment-specific behavior. For a simple zero-parameter list tool, this is adequate but not rich.

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 filler. The main action and resource are front-loaded, and the parenthetical output detail is the only extra information, which is necessary and concise.

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 listing tool with an output schema present, this description provides enough context for an agent to invoke it correctly: what it lists, what the output contains, and nothing else is required. The sibling context does not reveal a missing prerequisite or alternative that needs explanation.

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?

There are zero parameters, so the baseline is 4. The description adds value by clarifying what the returned templates contain ('name, mark') and narrowing the scope to 'available Vega-Lite chart templates'.

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 ('List') and a specific resource ('available Vega-Lite chart templates'), and it identifies the output fields ('name, mark'). This clearly differentiates it from sibling tools like strata_render_chart, which presumably consumes rather than lists 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 intended use is implied by the verb and resource: call this tool to enumerate available chart templates. However, it does not explicitly state when to use it instead of an alternative such as strata_render_chart, nor does it mention any prerequisite relationship between listing and rendering templates.

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