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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is not a pure read operation. The description adds useful security context by stating that access and refresh tokens are never accepted or returned, but it does not explain the side effects of starting authorization or what authorization creates or updates.

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 description is two tightly written sentences with no wasted text. The main capability is front-loaded, and the token-safety constraint follows efficiently.

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 five-parameter tool with full schema coverage and no output schema, the description covers the core purpose and a key security constraint. However, it does not describe what the connection/profile metadata contains, what starting authorization returns, or how operation-specific behavior differs, leaving some context gaps.

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 the schema already documents all five parameters, including operation-specific requirements for region, marketplaceId, and connectionId. The description does not add parameter-level semantics beyond what the schema provides, which is the baseline case for a fully documented schema.

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 uses a specific verb and resource: it starts Amazon Ads OAuth authorization or returns connection/profile metadata. It is clear about the tool's scope, but it does not explicitly differentiate itself from nearby siblings such as nexscope_data_amazon_ads_authorize_url or nexscope_data_amazon_ads_profiles.

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 explains what the tool does but gives no explicit guidance on when to use it versus alternatives. It does not clarify how to choose among operation=authorize, operation=connections, and operation=profiles, nor does it name sibling tools.

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