Delete scheduled EV assessment

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

The description merely restates the tool title and adds no behavioral context beyond what the annotations already declare. Annotations indicate destructiveHint=true and idempotentHint=true, but the description does not explain consequences like irreversibility or required permissions. It fails to provide any additional transparency.

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 wasted words. However, it is essentially identical to the tool title, making it redundant and lacking in informative value. While concise, it does not earn its place beyond restating the name.

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 simple nature of the tool and the presence of annotations, the description still lacks important context. It does not explain what schedule_id is, whether the deletion is permanent, or what effects it has on related entities. The description is too terse for reliable tool selection and invocation.

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 description does not mention the schedule_id parameter at all. With 0% schema description coverage, the agent receives no semantic guidance about what schedule_id represents or where to obtain it. The description completely fails to compensate for the 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 clearly states the tool's function: deleting a scheduled EV assessment. The verb 'Delete' is specific and the resource 'scheduled EV assessment' distinguishes it from sibling tools like cymulate_ev_scheduled_update and cymulate_ev_scheduled_get. This is a precise and unambiguous purpose statement.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or scenarios where a different tool would be preferred. The only implied usage is the action itself, but no explicit direction is given.

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