list_alerts

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

The verb 'List' conveys a read-only operation and 'need attention' adds a filtering trait, but the description does not disclose what the returned entries contain, whether only unresolved issues are included, or how the optional account parameter affects results. Since no annotations are provided, the description carries the full behavioral burden and only partially meets it.

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?

One concise, front-loaded sentence with no redundant filler. Every word contributes meaning, and the action verb appears first.

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 simple one-parameter list tool, the description gives the essential purpose and scope. However, with no output schema and no annotations, it does not clarify the response shape or the exact meaning of 'need attention,' leaving the agent to infer those details. It is adequate but not fully complete.

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%: the single 'account' parameter is already described as 'Account name. Auto-detected if omitted.' The tool description adds no additional parameter-level meaning, so the schema-based baseline of 3 is 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 uses a specific verb ('List') and a clear resource ('AdSense alerts and policy issues') with a scope qualifier ('that need attention'). It is immediately distinguishable from sibling list tools like list_accounts, list_ad_clients, and list_ad_units.

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?

The phrase 'that need attention' implies this is for reviewing actionable or notable alerts, but the description gives no explicit guidance on when to choose this over siblings or when it is not appropriate. The intended context is inferable, not stated.

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