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

Annotations already communicate idempotency (idempotentHint=true) and non-destructiveness (destructiveHint=false). The description adds little beyond the vague 'privacy-filtered project metadata', and it does not explain behavioral implications of required fields like idempotencyKey or expectedVersion. No contradiction with annotations, but minimal added value.

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?

The description is a single compact sentence, which is structurally efficient. However, it is so vague that it does not earn its place; the phrase 'privacy-filtered project metadata' is unclear and not front-loaded with the essential meaning.

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?

This is a complex mutation tool with 7 parameters, a nested object, no output schema, and annotations that only hint at idempotency. The description gives no information about behavior, return values, versioning semantics, or prerequisites. It is wholly inadequate for an agent to invoke correctly.

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 0%, so the description must compensate for the 7 parameters, including the nested 'details' object. It fails to mention any parameter, their roles, relationships, or constraints. An agent cannot infer what projectId, handoffId, idempotencyKey, expectedVersion, or details mean from this description.

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 action ('Update') and a resource ('hosted record chat handoff delivery'), which distinguishes it from the sibling create_chat_handoff. However, the phrase 'privacy-filtered project metadata' is ambiguous and the resource name is jargon, so it is not fully self-explanatory.

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?

No guidance is provided on when to use this tool versus alternatives such as create_chat_handoff or other update tools. There are no preconditions, exclusions, or context indicating the appropriate scenario for calling this tool.

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