vortex_remove_mod

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: removal spans ALL profiles for the game, the call is queued asynchronously, and it returns a job ID (useful since there is no output schema). It stops short of describing the job lifecycle or undo options.

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?

Three short sentences, front-loaded with the action, then scope, then warning and return value. Every sentence carries distinct information with no filler.

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?

With annotations covering the safety profile and no output schema, the description supplies the missing behavioral facts: destructive cross-profile scope, async job queueing, and the job-ID return. Only the ambiguous profileId parameter remains under-explained.

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 50%: modId is documented (sourced from vortex_mods) while profileId has no schema description. The description adds a relevant nuance – removal applies across ALL profiles – which explains the role of profileId in this operation, but it never describes either parameter directly.

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?

Clear verb+resource ("Queue removal of a local mod") with scope stated ("Removes it from ALL profiles for its game"). This distinguishes it from siblings like vortex_set_mod_enabled and vortex_install_download, though no sibling is named explicitly.

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?

"Inspect profiles before calling" gives a precondition, and "Destructive" signals caution. However, no alternatives are offered (e.g., disabling via vortex_set_mod_enabled instead of removing), so usage is implied rather than fully guided.

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