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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: that events are scoped to asset-type (never individual assets), that strategy resolution falls back from type to type group, and that pagination is automatic. It does not describe error or empty-result behavior, but the added context exceeds what annotations provide.

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 tightly packed sentences: identity and scope first, resolution semantics second, filters and the currency caveat last. Every clause carries information; nothing is repeated 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?

For a zero-required-parameter read-only list tool, the description covers identity, scope semantics, filter fields, resolution precedence, pagination behavior, and even a downstream currency caveat. It does not need to explain return values since no output schema exists, though a hint about what a lifecycle event record contains would be a marginal plus.

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%, so the schema already documents all six parameters including the pagination defaults and enum meanings. The description reiterates the filterable fields and adds the constraint that exactly one scope ID may be given, which maps to a real semantic (asset_type_id XOR asset_type_group_id) not fully spelled out in the schema. This is a slight enhancement over baseline.

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 and resource ('List facility lifecycle strategy events') and immediately distinguishes the tool from its sibling list_infrastructure_lifecycle_events by scoping to asset-type strategy events rather than infrastructure assets. The parenthetical definition of what an event is adds precision beyond the name.

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 explains the resolution rule (exactly one of asset_type_id or asset_type_group_id, and the effective-strategy precedence) and lists the filterable fields, which gives clear context for when to use this tool. However, it does not explicitly name alternative tools or state when this is the wrong choice versus get_asset_lifecycle_event or list_infrastructure_lifecycle_events.

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