List scheduled EV assessments

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

The readOnlyHint and idempotentHint annotations already convey that this is a safe, read-only operation. The description adds only the phrase 'all scheduled,' which is minimal extra behavioral context; it does not explain pagination, filtering behavior, or response details.

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 or redundancy: 'List all scheduled Exposure Validation assessments.' Every word contributes to the core purpose.

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 minimal schema (one undocumented nested query object), no output schema, and no parameter guidance, the description is not sufficient for an agent to invoke the tool with confidence in filtering or expected results. Annotations cover safety but not functional completeness.

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 optional 'query' object or its purpose. Since the schema provides only a generic additionalProperties structure, the description leaves the agent without any guidance on how to use the parameter.

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 scheduled Exposure Validation assessments.' clearly identifies the action (list) and the resource (scheduled EV assessments), and the word 'scheduled' distinguishes it from similar sibling tools like cymulate_ev_launched_list.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or related tools such as cymulate_ev_scheduled_get or cymulate_ev_scheduled_create.

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