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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description still adds genuinely useful non-obvious behavior: amounts are returned as bare numbers without currency, and a second call is needed to render them. That is exactly the kind of quirk annotations cannot express.

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?

Two tight sentences with zero waste. The core action is front-loaded, and the caveat about currency is deferred to second position where it belongs.

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 usefully compensates by warning about the unlabeled currency on returned amounts and pointing to the tool that resolves it. For a single-parameter read tool this is close to complete; only the relationship to the list sibling is unstated.

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% and the single 'id' parameter is documented as 'Lifecycle event ID' in the schema itself. The description only echoes 'by ID' at the same level of detail, adding no format or lookup semantics beyond the schema.

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 with scope: 'Get a single lifecycle strategy event by ID.' The word 'single' implies the contrast with list_infrastructure_lifecycle_events, but that sibling is never named, so differentiation is left partly to inference.

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?

Gives a concrete follow-up prerequisite ('call get_organization_settings for currency_code before stating one'), which is real usage guidance for interpreting the result. However, it never says when to use this tool versus list_infrastructure_lifecycle_events, and there are no exclusions or error conditions described.

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