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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so 'Non-destructive' largely restates structured data, and 'returns the updated name' is redundant because an output schema exists. It does confirm the narrow scope of the mutation (a rename, not a content overwrite), but adds little beyond the annotations.

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 compact sentences with the primary action first and the conditional mode immediately after; every clause carries information and nothing is padded.

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 an output schema, full parameter coverage and annotations covering safety, the description needs only to establish purpose and the two modes, which it does. Minor omissions (no guidance on renaming vs. general updates, no note on permission needs) keep it short of perfect.

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 documentId, name and tabId are fully documented in the schema, and the 60-character/ellipsis truncation rule lives there too. The description only echoes the tabId branch, adding no format or constraint detail beyond the schema, so the baseline 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 a document') plus the conditional variant ('with tabId, one of its tabs'), which is enough to distinguish it from sibling rename_diagram and from update_document. The two operating modes are declared up front without opening the schema.

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 parenthetical '(with tabId)' tells the agent which parameter selects the tab-renaming mode, which is genuine conditional guidance. However, it never states when to prefer rename_document over update_document, nor any prerequisites or exclusions, so usage remains implied rather than explicit.

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