Set mods

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

With no annotations, the description carries the burden. It explains the workshopId/modId distinction and load order implications, which is useful. However, it does not disclose whether the operation is atomic, reversible, or requires a restart, which is typical for a mutation tool. It does signal it's a write operation via 'Update' and 'add/remove/reorder'.

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 sentences, each delivering useful information: purpose, ID nuance, and usage guidance. No filler or redundancy.

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?

The description, combined with the fully-described schema, gives sufficient context for a setter tool. It explains the critical domain specifics (ID types, load order) and usage scope. The presence of an output schema handles return value documentation, so the description doesn't need to cover that.

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 schema covers all parameters at 100% coverage, so the baseline is 3. The description reinforces the need for both IDs and load order, but this information is already in the schema's mods parameter description, so it adds marginal value beyond the schema.

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 updates Mods and WorkshopItems together, and explicitly says it handles add/remove/reorder of the server's mod list. This distinguishes it from sibling pz_get_mods (which reads mods).

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 explicitly states when to use it: 'Call this for any add/remove/reorder of the server's mod list.' This gives clear context, though it doesn't explicitly exclude alternatives; the sibling pz_get_mods is obviously for reading, so the guidance is sufficient.

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