Reset an environment

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

With no annotations, the description carries the full burden and does well: it declares this is destructive ('Everything in it is deleted'), that it mutates a live environment, that confirm:true is required, and that omitting it yields a dry run. It still doesn't state irreversibility or whether a backup is taken first, which matters for a wipe operation.

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?

Front-loaded with the key purpose and danger, but 'requires confirm: true' is stated twice in slightly different wording, which is wasted repetition in a four-sentence description.

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 admin tool with no annotations and no output schema, the description covers purpose, blast radius, the confirm gate and the auth profile dependency. The remaining gaps (irreversibility/backup, return shape) are minor but non-zero for an operation this consequential.

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 coverage is 100% across 15 parameters, so the schema already documents every field. The description reinforces the gating semantics of confirm (dry run without it) but adds no syntax or value guidance for the other parameters beyond what the schema states, so baseline 3 is appropriate.

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 ('Reset an environment to an empty Dataverse instance') and the consequence in the same breath, which cleanly separates it from siblings like cs_admin_delete_environment, cs_admin_copy_environment and cs_admin_restore_environment.

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?

Gives clear conditions: the operation mutates a live environment, requires confirm: true, and otherwise returns a dry run, plus the note that it runs under the active pac auth profile. It does not explicitly name alternatives (e.g. delete vs. restore) for an agent weighing options, so it stops short of a 5.

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