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

The line "Credentials remain on the server" usefully explains that no auth material is needed at call time, which annotations do not cover. But "Mutations require preview and confirmation" implies this endpoint can mutate data, directly conflicting with the declared readOnlyHint=true and destructiveHint=false, leaving the agent unsure whether calling it has side effects.

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 are appropriately sized, but the leading sentence duplicates the title rather than front-loading the actual purpose, and the mutations sentence is generic boilerplate that actively misleads given the read-only annotation.

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 one-parameter, no-output-schema tool the description is thin: it never says what a profile record contains (profileId, account name, marketplace/country) or how the result is used downstream. Since other ad tools presumably need a profile identifier, omitting that linkage leaves a real gap for an agent planning a multi-step workflow.

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% for the single connectionId parameter, so the schema already explains that it selects a Nexscope-owned Amazon Ads connection. The description's "Uses your Nexscope Amazon Ads connection" merely echoes that, adding no format or retrieval guidance. Baseline 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 restates the title verbatim ("Amazon Ads: profiles API") and never supplies a verb or object-level statement of what the call returns. It does not distinguish this tool from dozens of ad-API siblings such as nexscope_data_amazon_ads_authorized_stores or nexscope_amazon_ads_manager, so an agent cannot tell which one surfaces profile records.

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?

There is no statement of when to call this versus the many other Amazon Ads tools, and no prerequisite ordering such as "call this first to obtain a profileId." The only usage-adjacent sentence ("Uses your Nexscope Amazon Ads connection") describes plumbing rather than selection criteria.

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