set_primary_build

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

Annotations already indicate that this is a mutating (readOnlyHint=false), idempotent, and non-destructive operation. The description adds the prerequisite that the build must be a completed publish build, but it does not disclose what happens to the previous primary build or whether an incomplete build causes an error.

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 a single, front-loaded sentence with no filler or redundant wording. It conveys the action, the object, and the key prerequisite efficiently.

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 simple one-parameter setter with annotations covering safety and idempotency, the description is largely sufficient. It identifies the essential precondition (completed publish build) and the tool's purpose, though it could mention how the buildId is obtained or whether the primary build is replaced.

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 only provides buildId as an integer with exclusiveMinimum 0, and schema description coverage is 0%. The description helps by indicating that the buildId must refer to a completed publish build, but it does not explicitly name the parameter or explain how to obtain a valid buildId.

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 operation: setting a completed publish build as the project primary build. It clearly distinguishes this from sibling build tools like create_build, get_build, list_builds, download_build, and delete_build.

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 phrase 'completed publish build' implies that only builds that have finished publishing are valid targets, providing a usage condition. However, it does not explicitly name alternatives or state when not to use this tool, so the guidance is implied rather than explicit.

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