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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — notably it never explains why a rename is flagged destructive (the previous name is replaced/lost) or whether the pid must belong to the caller, which is exactly the kind of context an agent needs before mutating.

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 or repetition. It is efficient, though its brevity borders on under-specification rather than genuine tightness.

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 described, and the two required parameters are fully documented in the schema. However, for a destructive, idempotent mutation, the description omits any note on side effects, permissions, or how it relates to edit_project, leaving a real gap.

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%, with both pid ('Existing Revid project id') and name ('New project name') documented in the schema itself. The description contributes no additional meaning such as naming constraints or whether the new name must be unique, so the baseline of 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 and resource ('Rename an existing Revid project'), which is unambiguous and tells the agent it operates on an already-existing project rather than creating one. It does not differentiate itself from the nearby siblings edit_project or duplicate_project, which could plausibly also change a project's metadata, so it stops short of a 5.

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 guidance and no mention of alternatives such as edit_project (which may also change project fields) or duplicate_project. The word 'existing' weakly implies the project must already be present, but that is the only usage signal and it is inference rather than guidance.

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