List EV input configurations

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which cover the safety profile. The description adds no extra behavioral context such as pagination, return format, or scope limitations. It merely restates the tool's name.

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 waste, but it adds little value beyond the tool name and title. It is concise but under-specified, bordering on tautological, since 'List all EV input configurations' essentially repeats the tool's name and title.

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?

Given the tool's simplicity (1 optional parameter, no output schema), the description is too sparse. It leaves unexplained the 'query' object's semantics, whether the list is paginated, and what fields are returned. For a list tool, this level of context is insufficient.

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?

Schema description coverage is 0% and the description does not mention the 'query' parameter at all. The parameter is an optional object with no property semantics defined, leaving the agent without any understanding of its purpose or format. The description fails to compensate for the schema gap.

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 verb 'List' and resource 'EV input configurations' clearly state the tool's function. It distinguishes from the sibling tools create/get/update/delete within the same resource family, but does not explicitly contrast with 'get' or other filtering options.

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. It does not mention that 'get' retrieves a specific configuration, nor does it explain the optional 'query' parameter for filtering. The sole sentence offers no usage context.

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