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

Annotations only declare readOnlyHint=false and openWorldHint=true. The description adds two things the annotations do not: credentials are held server-side (so only a connectionId is needed) and writes follow a mandatory preview-then-confirm protocol. It still doesn't describe what a mutation affects or what comes back, but the auth and safety context is a real contribution beyond the structured fields.

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 with no padding, which is appropriate in size. But the first sentence is a pure restatement of the title and earns little, and the useful operational facts (auth model, confirmation flow) are not front-loaded.

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?

This is an open-world passthrough proxy with a free-form `body` string and no output schema, so an agent needs to know what upstream payload shapes are acceptable and what a response looks like. The description covers neither, and it does not identify which Sponsored Brands target entities or operations this endpoint exposes, leaving a significant gap for an 11-parameter write-capable tool.

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 one of the 11 parameters is already documented in the schema, including the method/confirmationToken/pagination nuances. The description adds no parameter-level meaning beyond that, so the baseline of 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's substance is "Amazon Ads: sb/targets API", which simply restates the tool title/name. It never says what operation the tool performs (creating or modifying Sponsored Brands targets through a proxy) and gives no way to distinguish it from the many near-identical siblings such as nexscope_data_amazon_ads_developer_proxy_sb_targets_list, sd_targets, or sp_targets.

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?

"Uses your Nexscope Amazon Ads connection" plus "Mutations require preview and confirmation" implies the write workflow (preview first, then confirm with a token), which is genuine usage guidance. However, there is no statement of when to choose this endpoint over the sibling *_targets / *_targets_list tools, and no prerequisites or exclusions are given.

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