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

Annotations already flag a non-read-only, open-world operation. The description adds concrete behavior beyond that: credentials remain server-side and mutations require a preview-then-confirmation token flow. It still omits destructive effects and rate limits, but adds meaningful context.

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 resource name and then auth/confirmation details. There is no filler, though the first sentence is largely a title restatement and the description is terse for the tool's complexity.

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 an 11-parameter mutation proxy with no output schema and many sibling proxy tools, the description leaves out the actual operations (POST creation vs PUT modification), body payload requirements, and selection guidance against sp_targets_list. It is not complete enough to invoke correctly without reading the schema.

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% across 11 parameters, and the schema itself documents method, body, pagination, contentType, confirmationToken, and connectionId. The description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 first sentence is essentially the title repeated: "Amazon Ads: sp/targets API" names the upstream endpoint but gives no operation verb (create, update, list). It does not distinguish this mutation proxy from sibling nexscope_data_amazon_ads_developer_proxy_sp_targets_list, so an agent cannot tell the core purpose from the description alone.

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 when-to-use or when-not guidance is provided. The only procedural note is that mutations require preview and confirmation, but the description never says to choose this over sp_targets_list or which method/body scenarios apply.

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