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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail of what the log contains (status changes, portal syncs, webhooks, notes), but says nothing about retention, total volume, or how far back the trail goes.

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 short sentences, front-loaded with the core action, with no filler. Minor redundancy in 'audit trail / event log' and 'portal sync, webhooks' partially restating each other.

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?

An output schema exists, so return-value shape needn't be spelled out, and the description covers the resource, contents, and a use case. The remaining gap is routing guidance versus get_formation_status, which an agent must infer.

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 description adds no meaning beyond it — formation_id is not clarified and the limit/ordering behavior (default 50, max 500, newest-first) is only in the schema. Baseline 3 applies when the schema carries the parameter burden.

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 ('Return the full audit trail / event log for a formation') and enumerates the content (status changes, portal syncs, webhooks, notes). It implicitly differs from offshoreproz_get_formation_status by promising the full log rather than a snapshot, but it never draws that line 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?

'Useful for debugging or understanding where a formation is in the pipeline' gives a use case, but there is no when-not guidance and no named alternative, even though get_formation_status is the obvious competing choice for pipeline position.

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