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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds genuine context about Amazon-side access scoping ('Amazon grants access', 'accessible to an Ads profile'), but says nothing about pagination, rate limits, or freshness behavior for a live external API, so it adds only moderate value.

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, zero padding, and the payload-routing guidance (use the returned IDs for the Amazon-Ads-AccountId header) is front-loaded rather than buried.

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?

An output schema exists, so return-shape explanation is correctly omitted, and all parameters are self-documented. The remaining gap is operational: no note on default result sizing or whether the list is paginated, which matters for a live open-world discovery call.

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 (including limit, profile_id, advertiser_id, and the two include_* flags) are already fully documented in the schema. The description adds no syntax, format, or interaction detail beyond that, 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 a specific verb and resource ('Return Amazon-source DSP advertiser records') and scopes it to records 'accessible to an Ads profile.' It also explicitly frames the tool as a discovery step for IDs consumed by get_dsp_entities_live, so an agent can separate it from that sibling without opening either schema.

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?

It gives explicit usage context ('Use this to discover DSP advertiser IDs for the Amazon-Ads-AccountId header used by get_dsp_entities_live'), naming the downstream alternative and the ordering dependency. It stops short of stating when NOT to use it (e.g., when IDs are already known), which keeps it from a 5.

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