list_notification_policies

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'List', which implies a read operation, but it does not disclose pagination behavior, response contents, whether the result set is limited/ordered, or any rate-limit considerations. For a list tool this leaves meaningful behavioral traits to inference.

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?

A single six-word sentence contains the entire description with zero filler. The verb and core scope are front-loaded, and every word earns its place.

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 one-parameter list tool with no output schema and no annotations, the description is minimally adequate: it identifies the operation and the required account scope. However, it omits what the response contains, how pagination works, and how this tool relates to the sibling notification tools, leaving an agent to guess at call expectations.

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% since account_id is already documented as 'The account ID'. The description adds no parameter-level detail beyond the schema, so the baseline 3 for high coverage applies.

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 ('List'), a specific resource ('notification/alerting policies'), and a scope ('for an account'). It is clear and distinguishable from same-domain siblings like list_notification_history, list_available_alerts, and list_notification_webhooks because the resource term 'policies' is precise. However, it does not explicitly contrast itself with those siblings.

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 guidance on when to use this tool versus alternatives such as list_notification_history, list_notification_webhooks, or list_available_alerts. The description provides no context for tool selection, no exclusions, and no mention of prerequisites or related tools.

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