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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds a real behavioral fact beyond them — the owner/admin permission requirement — plus a hint that renameVariants cascades to reports. It does not say what happens on unauthorized calls, on name collisions, or whether the rename is reversible.

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 sentences with the main action front-loaded and the permission caveat last — no filler. The phrase "and answers it" is wasted space that reads as an odd synonym for returning the updated burst.

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 mutating tool with annotations and no output schema, the definition covers purpose, authorization, and the cascade flag. It is still thin on mutation-relevant concerns an agent needs: error mode when not owner/admin, name-uniqueness rules, and what the response contains.

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?

Top-level schema description coverage is only 33%, but the nested properties (name, renameFiles, renameVariants, id) are already well documented in the schema. The description contributes one piece of semantics beyond the schema: that renameVariants also renames the burst's reports. It says nothing about the idempotencyKey or the id lookup.

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 is explicit ("Renames a burst") and it names the optional extension ("with renameVariants its reports too"), so an agent can distinguish it from updateBurstSettings or duplicateReport. The phrasing "and answers it" is cryptic and slightly muddies the statement of what the call actually returns.

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?

There is no explicit when-to-use statement or routing to alternatives; the agent is left to infer that renaming a burst belongs here rather than in updateBurstSettings. The only genuine usage constraint given is the authorization precondition ("Only the burst's owner and admins may").

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