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

The annotations already declare openWorldHint=true and destructiveHint=true, so the agent knows this is not a purely read-only operation. The description adds a useful security constraint—tokens are never accepted or returned—but it does not explain the side effects of starting OAuth, whether a connection is created, or what metadata is returned.

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?

Two sentences, front-loaded with the primary actions, and no wasted text. The token-handling note is a concise and relevant caveat.

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 multi-operation tool with no output schema, the description is somewhat sparse. It does not clarify what authorize returns (for example, a URL), what connections or profiles contain, or how the operation modes differ behaviorally, though the schema does carry parameter-level details.

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 all five parameters are already documented in the schema, including conditional requiredness for region, marketplaceId, and connectionId. The description adds no further parameter semantics beyond what the schema provides, making the baseline 3 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 description states two specific capabilities: starting Amazon Ads OAuth authorization and returning connection/profile metadata. It is clear about the resource, but it does not explicitly distinguish this access tool from siblings like nexscope_amazon_ads_manager or nexscope_data_amazon_ads_authorize_url.

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 phrase 'Starts Amazon Ads OAuth authorization or returns safe connection and profile metadata' implies the two main modes, and the operation parameter enumerates choices. However, there is no explicit guidance on when to choose this tool versus related Amazon Ads tools, nor are prerequisites or operation-selection conditions stated.

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