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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description's 'Overwrites the current build name' usefully confirms what is destroyed (the prior name) and aligns with the annotations, but it says nothing about permissions, error behavior, or what the call returns.

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?

Two short, front-loaded sentences with no waste; the core action comes first and the overwrite caveat follows immediately.

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 two-parameter mutation with full schema coverage and rich annotations, the description is nearly sufficient. The only gap is the return value, which matters slightly since there is no output schema, but it is minor for a rename operation.

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 both parameters (buildId, name) are documented in-schema, so the baseline is 3. The description mentions the name being replaced but adds no syntax, format, or constraint detail beyond what the schema already provides for 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?

States a specific verb (renames) and resource (TestMu AI web automation build) with the additional scope note that it overwrites the existing name. An agent can tell it apart from deleteBuild/stopBuild by the verb alone, though no sibling is named explicitly.

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?

Usage is implied by the verb 'Renames' and the overwrite warning, but there is no explicit when-to-use guidance, no prerequisites, and no pointer to alternatives such as deleteBuild or stopBuild for other build lifecycle operations.

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