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

The annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is known; the description adds genuine value by stating that server-owned fields are excluded and that approval requirements are governed by the org admin and business workflow rules. However, for a destructive non-idempotent update over a 60+ field object it never states whether this is a full replacement or a partial merge, nor what happens to omitted fields — a significant gap given destructiveHint=true.

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 tight clauses with the action front-loaded and no filler. The approval sentence is somewhat opaque in wording but is not padding, so the structure largely earns its space.

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 explained, but the complexity here is high: a destructive, non-idempotent update to a deeply nested object with zero parameter documentation. The description supplies neither update semantics (merge vs replace), a listing of immutable/server-owned fields, nor any guidance on the approval gate that gates success.

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% across a nested object with dozens of properties, so the description carries the burden — yet it says nothing about the required id or data parameters, field formats, or which specific properties are server-owned. "Server-owned fields are excluded" is a useful hint about writability but leaves the agent to guess which of the ~60 fields fall into that category.

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?

"Configure/edit criteria_profile" names a verb and resource, so the basic intent is inferable, but it largely restates the tool name and never says what a criteria profile represents or what kinds of fields are being edited. It makes no attempt to distinguish itself from create_criteria_profile, get_criteria_profile, archive_criteria_profile, or delete_criteria_profile beyond the verb.

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 statement of when to reach for this tool versus the create/get/archive siblings, and no prerequisites or preconditions for editing are given. The approval sentence describes a policy condition but does not tell the agent when to choose this tool over alternatives.

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