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

Annotations already flag the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the bar is lower, yet the description adds non-obvious behavioral context: the slug is immutable, tags must pre-exist, applying or removing a tag 'can change who reaches the project' (an access-control side effect), and Admin rights are required. These are exactly the hidden consequences an agent needs and that annotations cannot express.

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?

Four short sentences, front-loaded with the core action, then constraints. Every sentence carries distinct information (scope, slug invariance, tag prerequisite, permission) with no filler or repetition.

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?

With no output schema, the description could say more about the result of the update, but it is otherwise complete for a 3-param mutation: it covers purpose, prerequisites, auth, and side effects. Return/failure behavior is the only notable omission.

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%, so the baseline is 3; the description nonetheless adds meaning beyond the schema by stating that the slug never changes and that tags must already exist, both of which govern how 'name' and 'tags' should be supplied. The information is real but thin, so it sits modestly above baseline.

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 verb and resource: renaming a project and setting its tags, anchored to the familiar Settings › Projects drawer. It also preempts a common confusion with 'the slug never changes', which separates it from rename-style siblings. It falls just short of 5 because it never names a contrasting sibling tool directly.

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?

It gives real operational context: tags must already exist and points the agent at list_tags to obtain them, plus the 'Needs project Admin' prerequisite. It does not, however, say when to prefer this over adjacent tools like set_project_caps, archive_project, or rename_tag, so it stops short of explicit alternatives.

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