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

Annotations declare readOnlyHint=true and destructiveHint=false, yet the description states "Mutations require preview and confirmation," implying the tool performs writes. That directly conflicts with the declared read-only profile. The one genuinely useful addition, "Credentials remain on the server," does not offset the contradiction.

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?

It is short and front-loaded, but the lead sentence is a tautological restatement of the title and the trailing mutation sentence spends space on a contradictory claim rather than on real information.

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 token/credential-related tool with no output schema and openWorldHint=true, the description never says what is returned, whether a token is issued or merely stored/queried, or how failures (expired/invalid connection) surface. Given the dense cluster of Amazon Ads auth siblings, this is insufficient to call the tool correctly.

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?

There is a single parameter with 100% schema description coverage ("An Amazon Ads connection owned by the authenticated Nexscope user"), so the schema already carries the meaning. The description adds nothing about connectionId or what happens with additionalProperties: true.

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?

"Amazon Ads: store Tokens API" essentially restates the tool name and title without explaining what actually happens — whether tokens are read, written, listed, or validated. It does not distinguish this from near-siblings such as nexscope_data_amazon_ads_refresh_token, nexscope_data_amazon_ads_authorized_stores, or nexscope_data_amazon_ads_authorize_url, so an agent cannot tell which one applies.

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 no when-to-use guidance, no prerequisites, and no exclusions relative to the many other Amazon Ads credential/connection tools in the sibling list. "Uses your Nexscope Amazon Ads connection" is context, not a selection rule.

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