agent_rename

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent); the description adds the non-obvious behavior that omitting 'name' actively clears the existing name, which is exactly the kind of surprise an agent needs flagged. It also reveals a uniqueness constraint, implying possible collision errors. It does not say what happens if 'target' does not exist.

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?

A single front-loaded sentence with no filler. The clear-on-omit rule is attached directly to the action it modifies rather than buried.

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?

An output schema exists, so return values need not be explained, and the mutation semantics are partially covered. However, for a two-parameter mutation tool with zero schema descriptions, the missing definition of 'target' and the absence of any collision/error behavior leave an agent guessing at invocation details.

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 0%, so the description carries the whole burden. It gives real semantics for 'name' (unique, nullable, omit-to-clear), but leaves the required 'target' parameter completely unexplained — no hint whether it is an id, a name string, or how to obtain it.

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 ('Give... a unique name' / clear) and resource ('an agent'), which cleanly separates it from the many sibling *_rename tools (workspace_rename, pane_rename, tab_rename). It never explicitly names those siblings, but the resource scope is unambiguous.

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 implies the two modes of use (supply a name to set, omit it to clear) but gives no guidance on when to prefer this over alternatives, nor any prerequisite such as the agent existing. Usage is inferable rather than stated.

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