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

Annotations already establish readOnly/idempotent/non-destructive, so the description earns credit for additive context: it discloses that URLs and signing secrets are excluded from results, warns that 'live state may change', and states the tickets:read scope. That is meaningful disclosure beyond the structured hints.

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?

Four tight sentences with the purpose front-loaded; exclusions, pagination, and auth each earn their place. No filler, though the mix of param filters and output-field guidance in one clause is slightly compressed.

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 must hint at return shape, and it does (excluded secrets, has_more/next_before_id cursor). Auth requirement and freshness caveat are covered; only the enum-state semantics and limit behavior remain thin for a 0%-coverage schema.

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 coverage is 0%, so the description carries the burden. It maps meaning onto two of the four params ('optional rule' = rule_id, 'current state' = state) and explains pagination via next_before_id/has_more, but 'limit' is unexplained and the nine enum state values are not described. Partial compensation only.

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 owned notification delivery metadata') plus scope ('owned') and filter dimensions ('by optional rule and current state'). It distinguishes itself reasonably from the singular get_attention_notification_delivery sibling, though it never names an alternative explicitly.

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 description implies usage via the filter dimensions and supplies pagination guidance ('Follow next_before_id while has_more') and an auth prerequisite ('Requires tickets:read'), but it never says when to use this list tool versus the other attention-notification list/get siblings.

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