Create or update environment

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

Annotations only supply destructiveHint=false, so the description carries most of the burden, and it does add useful non-schema behavior: idempotent upsert semantics keyed on `id` and a concrete cost profile ('one API call, about 0.5s'). It does not disclose what happens to omitted fields on update (overwrite vs. preserve), which is the main remaining risk for a mutate tool.

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, zero filler: purpose first, the decisive id rule second, the discovery hint and cost last. Nothing is buried and nothing repeats structured fields verbatim.

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 6-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, create/update routing, discovery and cost — enough to call it correctly. It leaves unaddressed what the call returns on create (e.g., generated id) and the update-merge behavior, which are the only meaningful gaps.

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 description coverage is 100%, so the schema already documents id, code, host, slug, title and description. The description's only parameter-level statement ('with `id` it updates') duplicates the schema's own id description, adding no new syntax or constraint detail. Baseline 3 applies.

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 pair and resource ('create or update an environment') and clarifies the domain concept ('a named target such as staging or production that runs are attributed to'). The upsert duality is resolved immediately, so an agent can distinguish this from qase_environment_delete or the other *_upsert siblings without opening the schema.

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 the decisive routing rule — 'With `id` it updates, without it creates' — and points to qase_project_context as the place to discover existing environments, which is real guidance rather than implication. It stops short of stating when not to use it (e.g., bulk creation or deletes), so it is clear but not exhaustive.

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