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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description earns credit for adding domain behavior instead: events are scope-keyed and resolve by most-specific match, and amounts are bare numbers requiring a separate currency lookup. That cross-call currency requirement is behavioral context an agent cannot get from structured fields.

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 sentences, front-loaded with the core scope concept before filters and the currency caveat. Dense but each sentence carries distinct information; the scope-resolution analogy is efficient but slightly abstract.

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?

No output schema exists, so the description carries the return-value burden and does so partially by flagging that amounts are currency-less and how to resolve currency. For a six-param, zero-required list tool with full annotation coverage, this is sufficient, though return shape (fields, pagination behavior) is only lightly touched.

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 100%, so baseline is 3, but the description adds meaningful semantics on top: feature_class and material are described as scope keys (with an optional diameter band) rather than plain filters, and it ties the returned amounts to a currency resolution step. This goes beyond the terse schema descriptions.

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 (List) and resource (lifecycle strategy events) and immediately scopes it: condition-triggered maintenance/rehabilitation keyed on a scope, never on individual features. This distinction separates it from the sibling list_asset_lifecycle_events, which operates at the feature/asset level, without opening either schema.

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?

Names the four filters (feature_class, material, event_class, is_active) and gives a concrete cross-tool workflow step: call get_organization_settings for currency_code before stating an amount. It provides clear context for use but does not explicitly state when NOT to use this tool versus list_asset_lifecycle_events; the separation is implied by the scope definition.

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