List smart templates

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

Annotations already declare readOnlyHint and idempotentHint, so the safe read behavior is covered. The description adds the 'all' scope but does not explain pagination, filtering, or return format, which are minor gaps for a simple list tool.

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 unnecessary words, front-loaded with the action and resource. It is highly concise and easy to parse.

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?

The tool is a simple list operation with one optional query parameter, but the undocumented parameter is a notable gap. Given the rich sibling context and the lack of output schema, the description could have briefly mentioned filtering behavior or response contents to be fully complete.

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 one optional 'query' object with 0% schema description coverage. The description does not explain the purpose of this parameter, leaving the agent unsure how to use it for filtering. Since schema coverage is low, the description should compensate, but it remains silent.

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 'List all EV smart templates' uses a specific verb ('List'), a clear resource ('EV smart templates'), and explicitly says 'all', indicating the full collection. It distinguishes itself from sibling tool 'cymulate_ev_templates_list' by specifying 'smart 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 usage for retrieving smart templates but does not explicitly state when to choose this over other template/list tools. No alternatives or exclusions are mentioned, though the name and description make the scope reasonably clear.

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