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

Annotations only establish that the tool is mutating, idempotent, and non-destructive. The description adds substantial behavior beyond that: partial-patch semantics, array replacement semantics, null-clearing, owner/admin key requirements, recomputation of the product embedding, and non-metered status. This gives an agent a complete, accurate effect-and-cost model before invocation.

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 compact yet information-dense: purpose is front-loaded, followed by patch semantics, authorization, side effects, and metering. Every clause earns its place, and no sentence is redundant with the schema or annotations.

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 16-parameter mutation tool with no output schema, the description covers all essential operational context: what is updated, how partial updates work, who may call it, what happens on save, and whether it is metered. The per-field details are fully covered by the schema, and there is no critical missing guidance.

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 the baseline is 3, and the schema already documents each field including Pro-only flags and max lengths. The description adds cross-cutting semantics that apply to all parameters: only passed fields change, arrays replace stored lists, and nullable strings accept null to clear. This significantly improves an agent's understanding of how to construct a patch request.

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 uses a specific verb-resource pair ('Update your organization's product profile') and anchors it to get_product_profile, making the relationship to a sibling tool explicit. It also states what the profile is used for (research and reply features), so an agent can distinguish this from read-only or alert-related updates across the 46 siblings.

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 description gives clear behavioral context: it is a partial patch, arrays replace lists, and nullable strings clear values. It does not explicitly enumerate when to choose this tool over alternatives, but by naming get_product_profile and describing the update semantics, the intended usage is strongly implied and unlikely to be confused with sibling update tools.

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