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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by naming the returned fields (role, model, runtime, accepted steps, jobs) and the NIGHTSHIFT-paid scope, but says nothing about result size, ordering, pagination, or what happens when no seats match.

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?

One compact sentence with no filler, and the scope qualifier leads. It is slightly telegraphic — the field list after the colon reads like clipped notes rather than prose — but nothing extraneous is present.

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 no output schema, the description must carry the return shape, and listing the five fields does that adequately. However, for a filtered roster over 'orders NIGHTSHIFT paid for', it omits how results are bounded or ordered and whether the caller needs any prior state, leaving an agent to discover those by trial.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. The description spends its words on the result shape instead, which is the right allocation for a no-arg lookup.

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 identifies a specific resource set — IMD swarm seats that worked NIGHTSHIFT-paid orders — and lists the fields returned, which goes beyond restating the name. But it is a noun phrase with no verb ('list', 'get'), so the operation is only implied, and it does not distinguish itself from the nearby sibling `crews`, which reads like a very similar roster lookup.

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?

There is no when-to-use guidance at all: no indication of when to call this versus `crews`, `swarm_job`, or `imd_swarm`, and no mention of prerequisites such as needing a NIGHTSHIFT context or token first. The scoping phrase 'that worked on orders NIGHTSHIFT paid for' is the only implicit filter.

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