Programmability List Notification Integrations

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds only return-field trivia (quoted_name, quoted_qualified_name), which is redundant given an output schema exists, and says nothing about filtering, pagination or scope behavior.

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?

Purpose is front-loaded in the first sentence, which is good, but the second sentence spends space explaining return columns already declared in the output schema while the single input parameter goes unexplained.

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 an output schema present, the description should focus on scope, siblings and the undocumented 'pattern' parameter, but it instead duplicates return-value detail. It leaves the one input parameter and the sibling disambiguation entirely unaddressed.

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?

There is one parameter ('pattern') with 0% schema description coverage, and the description never mentions it, so an agent gets no indication of what a pattern filters on (name? qualified name? wildcard syntax?). This is the one place the description needed to compensate and it does not.

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 and resource ('List notification integrations') and enumerates the kinds of integrations covered (alerts, tasks, cloud messaging, SNS/PubSub/Webhooks). However it never distinguishes itself from the closely-named sibling 'programmability_list_integrations', so an agent could confuse the two.

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 rather than 'programmability_list_integrations' or other list tools, and no mention that the pattern parameter can be used to filter. Usage is only implied by the name and description.

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