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 meaningful detail that results are scoped to the authenticated API key and that each record surfaces status, jurisdiction, and next required actions, but says nothing about pagination, ordering, or empty-result behavior.

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 short sentences, front-loaded with the scope statement, with no filler. The second sentence partly restates what the output schema already conveys about returned fields, which costs it a point but does not make the text wasteful.

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 an output schema, rich annotations, and 100% parameter coverage, the description only needs to establish scope and purpose, which it does. Missing pagination and ordering hints are minor given how much the structured fields already carry.

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 limit, status, and jurisdiction are already fully documented in the schema, including the status enum values and jurisdiction codes. The description adds no filtering guidance beyond that, so the baseline 3 applies.

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 all formations') plus the scoping constraint ('for the authenticated API key'), which an agent can distinguish from the singular offshoreproz_get_formation_status. It stops short of naming the sibling tools explicitly, so it is clear but not maximally differentiating.

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?

Usage is only implied: the word 'all' suggests a broad enumeration versus the single-formation status/events tools, but the description never states when to prefer this over offshoreproz_get_formation_status or offshoreproz_list_documents, nor any prerequisite or pagination guidance.

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