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

Annotations already declare destructiveHint=true and idempotentHint=false, so the mutation risk is covered; the description adds genuine value beyond them by documenting the confirm=false dry-run preview and the 'create returns its id' return behavior. It does not discuss permissions or reversibility of remove/detach, keeping it from a 5.

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 scope-defining clause is front-loaded in the first sentence, followed by a tight per-action parameter map, then the keyword syntax and dry-run note. Every line earns its place with no filler.

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 7-parameter, multi-action mutation tool with an output schema available (so return values need not be described), the definition covers actions, required inputs, keyword encoding, and dry-run safety. Only customer_id and any permission prerequisites remain unstated, a minor gap.

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?

With 0% schema description coverage the description carries the parameter burden and largely does: action enum values, name, shared_set_id, campaign_id, confirm, and the keywords matching-type syntax ('text|EXACT'/'BROAD'/'PHRASE', default PHRASE). Only customer_id is left unaddressed (though it is a required account-scoping field).

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 (manages) plus the precise resource scope ('SHARED negative keyword lists, Shared Library, account-level') and names the sibling list_shared_negative_lists to anchor what it operates on. An agent can distinguish it from campaign-level tools like add_negative_keyword or manage_keywords without opening any schema.

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?

Enumerates five actions with the parameters each requires, effectively telling the agent which branch to select, and explicitly frames reads as belonging to list_shared_negative_lists. It lacks an explicit 'when not to use' clause, but the action map plus the sibling reference gives strong routing guidance.

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