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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description usefully adds that credentials stay server-side and that mutations go through a preview-and-confirm flow — real behavioral context not encoded in the annotations. It still omits what the mutation surface actually is or what a response looks like, keeping it below top marks.

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, front-loaded with the resource and followed by the operational constraints; zero padding. The brevity is efficient, though it comes at the cost of under-specification rather than trimming redundancy.

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?

With no output schema and an unclear operation set, an agent cannot tell what this call returns or which Amazon Ads profile actions it exposes. For a tool sitting next to dozens of Amazon Ads siblings, the description leaves the essential disambiguating information out.

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?

Only one parameter exists and schema coverage is 100%, so the schema already fully documents connectionId. The description adds no syntax, format, or selection guidance for it, which is acceptable at this baseline but not value-adding.

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 essentially restates the name and title ("Amazon Ads: profiles API") without saying what operation is performed — list profiles, get a profile, or something else. Among many Amazon Ads siblings (nexscope_amazon_ads_manager, nexscope_amazon_ads_api_access, the developer_proxy family), nothing distinguishes this tool's specific scope.

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 use this tool versus the many other Amazon Ads tools in the sibling list, and no prerequisites beyond the implicit connection requirement. The only actionable guidance, that mutations require preview and confirmation, is a workflow rule rather than usage selection guidance.

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