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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantial context beyond them: the row keeps its database identity, all inbound/outbound links survive, an ID-grid row's id cell is synced, and cached link labels are refreshed project-wide. This is exactly the kind of side-effect disclosure a mutation tool needs.

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?

Front-loaded with the core action, then side effects, then the delete-and-reinsert alternative, then the batch guidance. Dense but every sentence and parenthetical carries distinct, useful information.

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 3-param mutation tool with no output schema, the description covers what changes, what is preserved, side effects, and whether a follow-up read is needed. Nothing an agent needs to invoke it correctly is missing.

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 100%, so documentId, fromItemId, and toItemId are fully documented in the schema. The description adds only marginal meaning (the 'anchor by TraceID' re-read guidance), so baseline 3 is appropriate.

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 (rename) and resource (a row's visible TraceID) and clarifies scope by naming the two row types it applies to (traceable row, ID-grid row). An agent can distinguish it from the doc-level sibling traceable_doc_rename_prefix, which renames a prefix rather than a single row's TraceID.

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?

Explicitly instructs to use this instead of delete-and-reinsert because that would break links, and explains the batch pattern for renumbering a grid (call once per row). It gives both when-to-use and the preferred alternative, leaving little to inference.

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