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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond that: the data is LIVE/current, it deliberately excludes performance metrics, and an empty result is a valid answer that must not be fabricated.

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 telegraphic sentences, front-loaded with the LIVE nature and return contents, then routing, then the anti-hallucination rule. Every clause carries distinct information with no padding.

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, the description usefully explains what is returned (bid, state) and the empty-list meaning. However, the filtering parameters that determine which targets appear are left entirely undocumented, so an agent cannot confidently construct filtered calls.

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 20% (only account_id is documented) across 5 parameters. The description hints that results are scoped to 'questo profilo' but never explains state_filter, campaign_id, ad_group_id, or profile_id semantics, so it fails to compensate for the coverage gap.

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+resource ('LIVE ... product target Sponsored Brands') and enumerates the target kinds (ASIN/categoria/brand) plus the fields returned (BID e stato ATTUALI). It clearly distinguishes itself from sibling list tools such as ads_list_sp_targets and ads_list_sb_keywords.

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?

Explicitly routes the agent: the returned target_id feeds ads_update_sb_target_bid, and performance questions belong to execute_sql on the data-hub. It also instructs how to handle the empty-list case, which is real when/when-not guidance.

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