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

No annotations are provided, so the description carries the behavioral burden. It indicates the response includes days remaining and SeaReady verification timestamps, which helps an agent assess freshness, but it does not explicitly state that this is a read-only query or describe any data-source or rate-limit 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?

The description is a single front-loaded sentence that states the core resource first, then adds examples and secondary freshness information. Every clause earns its place, and there is no wasted text.

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 and no annotations, the description still explains the main return content: upcoming dates, days remaining, and last-verified timestamps. It is nearly complete for a low-complexity, one-parameter retrieval tool, though it does not describe return ordering, empty results, or update cadence.

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 within_days parameter is fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema already provides, 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?

The description clearly identifies the resource: upcoming dates in vetting and PSC regimes, with concrete examples such as concentrated inspection campaigns and RightShip rule changes. It does not explicitly distinguish itself from sibling tools like psc_checklist or sire_question_lookup, so it falls short of a 5.

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?

The usage is implied by the content: an agent can infer this tool is for checking upcoming inspection-regime deadlines. However, the description gives no explicit when-to-use guidance, no exclusions, and does not name alternatives.

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