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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds no further behavioral context such as pagination, return format, or filtering behavior, so it does not enrich what the annotations already provide.

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 a single, front-loaded sentence with no wasted words. However, it is so sparse that it fails to earn its place as useful context, making it concise but under-specified rather than optimally structured.

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 list tool with four optional parameters and no output schema, the description is incomplete. It does not clarify what is returned, how to filter by campaign/ad group, or what 'SP' refers to, leaving the agent with insufficient information to call the tool correctly in context.

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 only 25%, and the description mentions none of the four parameters (account_id, profile_id, ad_group_id, campaign_id). With low coverage, the description should compensate by explaining parameter meaning or filtering behavior, but it provides no parameter semantics at all.

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?

States a specific verb (List) and resource (SP negative product targets), which is enough to distinguish it from sibling list tools like ads_list_sp_targets or ads_list_sp_negative_keywords. However, it does not explicitly differentiate from those siblings or explain what 'SP' means, leaving some ambiguity for an agent unfamiliar with the domain.

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?

Provides no guidance on when to use this tool versus alternatives, nor any prerequisites or context. The name implies it lists negative product targets, but the description does not say when an agent should choose this over ads_list_sp_targets or ads_list_sp_negative_keywords.

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