List EV templates

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

The annotations declare readOnlyHint=true and idempotentHint=true, which already establish this as a safe read operation. The description adds the 'all' scope but omits any additional behavioral context such as pagination, filtering via the query parameter, or potential large response sizes. This meets the minimum bar but does not exceed it.

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, front-loaded sentence with no filler words. It is appropriately sized for a simple list operation, but the lack of parameter or return information prevents a perfect score for structure, as additional useful details could have been included without becoming verbose.

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 list tool, the description is minimally adequate but leaves significant gaps. The query parameter is completely unexplained, no return format is indicated (though no output schema exists), and there is no context about how this differs from the many sibling list tools. The description does not fully equip an agent to use the tool correctly, especially regarding the optional query.

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 parameter 'query' with no description in the schema (0% coverage), and the description does not explain what this parameter does or how it affects the results. In fact, saying 'List all' could be misinterpreted as meaning the query parameter is irrelevant. The description adds no value to the schema and fails to compensate for the complete lack of parameter documentation.

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 the specific verb 'List' and explicitly names the resource 'Exposure Validation templates', clearly distinguishing this from sibling tools like cymulate_ev_smart_templates_list or cymulate_template_groups_list. The word 'all' clarifies the scope as returning the full set of 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?

No guidance is provided on when to use this tool versus alternatives such as cymulate_ev_templates_get, cymulate_ev_smart_templates_list, or cymulate_advanced_list_templates. There is no mention of exclusions, prerequisites, or preferred contexts, leaving the agent to infer usage from the name alone.

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