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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is largely carried by structured data. The description adds the natural-language parsing behavior and instant-scoring option, but crucially does not say whether updating replaces or merges existing filters, which matters most 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?

Three short sentences, front-loaded with the primary capability (natural language) before the alternative (direct fields). Minimal waste, though the second sentence's example slightly overlaps the schema's own example.

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?

There is no output schema, and the description only hints at return behavior via the request_instant_scoring note. For a destructive mutation tool, the missing explanation of replace-vs-merge semantics leaves a meaningful gap, though annotations cover safety.

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 every parameter is already documented with examples. The description reiterates the field categories (industries, locations, employee sizes, buying signals) without adding 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?

The description states a specific verb+resource (update targeting preferences) and adds a distinguishing mechanic (natural-language ICP parsing). It does not name the read-only sibling get_targeting_preferences, but the write intent is unambiguous.

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?

It implicitly clarifies two usage modes (free-text ICP vs direct field specification), which is useful context. However, it never states when to use this versus get_targeting_preferences or get_saved_filters, nor any prerequisites.

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