update_test_collection

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

Beyond the idempotent and non-destructive annotations, the description discloses an important behavioral trait: 'Only provided fields are updated; omitted fields remain unchanged.' This is critical for correctly invoking a partial update and prevents unintended overwrites. It also implies a stateless merge behavior, adding value over the annotations alone.

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 description is two concise sentences with no filler. The primary action is front-loaded, followed by the update semantics and a helpful get-first instruction, making every sentence valuable.

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 7-parameter update tool with 100% schema coverage and meaning-bearing annotations, the description supplies the missing execution model: partial update, preserving omitted values, and for prospective state. It does not describe the response shape, but no output schema is defined and the description already gives enough to invoke the tool safely. A slight esponse-type note would make it fully complete.

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% and each parameter already has a clear description, including enum restrictions for status and priority. The description adds that fields are updated only if present, but it does not need to go into parameter details. Given the 100% schema coverage, the baseline is correct.

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 states a specific verb and resource: 'Update test collection metadata.' It clearly distinguishes from sibling tools like update_folder and update_test_case by honoring collection metadata. It is not a tautology and gives an immediate sense of the tool's purpose.

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 explains when to use the tool and a key precondition: 'Use get_test_collection first to see current values.' It also clarifies that only provided fields are updated, so an agent knows to send only the fields that need changing. It does not explicitly exclude alternatives, but the guidance is sufficient for a read-before-patch workflow.

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