Delete multiple TestMonitor milestones in one request, moving them to trash for later restoration.
Delete multiple milestones. Delete multiple milestones in a single request. Deleted milestones are moved to the trash and can be restored later if needed.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description still adds real value by disclosing that deleted milestones go to the trash and are restorable, which is not derivable from the annotations or schema and directly informs risk assessment.
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 first two sentences are near-verbatim repetition ('Delete multiple milestones' / 'Delete multiple milestones in a single request'), which is wasted space. The third sentence is the only one that earns its place, so the structure is loose but not bloated.
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 destructive batch mutation with no output schema, the restore-trash behavior is covered, but nothing is said about response shape, partial-failure behavior when some ids are invalid, or batch size limits. Minimum viable but with clear gaps.
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% at the top level and the description says nothing about the body payload, its shape, or valid id values. With one undocumented required parameter, the description fails to compensate for the coverage 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?
States a specific verb and resource ('Delete multiple milestones') and implies batch scope via 'in a single request', which separates it from the singular delete_milestone sibling. It stops short of naming the sibling explicitly, so a 4 rather than a 5.
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 on when to choose batch deletion over delete_milestone, no mention of limits on how many milestones can be deleted, and no prerequisites. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.