workload_save

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description's '(create, replace or rename)' usefully signals upsert semantics beyond the annotations, but says nothing about permissions, what state a replace overwrites, or side effects on saved runs.

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?

A single compact sentence with the verb front-loaded and no filler. The parenthetical is dense but earns its place by enumerating the modes.

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?

There is no output schema and no annotation-level detail about the opaque nested workload payload, permissions, or failure modes. For a save/upsert tool accepting an unstructured object, the definition leaves an agent under-equipped to construct a valid call.

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 0% and the required 'workload' parameter is a bare object with additionalProperties=true, so its structure is entirely undocumented. The word 'rename' hints that original_name carries the prior name, but that is the only semantic added and the payload shape remains a guess.

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 verb+resource pair ('Save a workload') is unambiguous, and the parenthetical '(create, replace or rename)' names the three modes of operation. This distinguishes it from siblings like workload_delete, workload_list, and workload_run, though it doesn't explicitly contrast with workload_define.

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 when-to-use guidance is given. An agent cannot tell from this description whether to call workload_save, workload_define, workload_update_statement, or workload_from_history for a given intent. The parenthetical lists modes but not selection conditions.

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