list_port_events

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

With no annotations provided, the description carries the full behavioral burden. It discloses global scope and that the events are arrivals/departures, and 'List' implies a read-only operation. However, it does not mention pagination, default time behavior, ordering, or response contents, which are important for a 9-parameter filter tool.

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 sentence that front-loads the verb and resource, then compactly summarizes the optional filter groups. There is no filler, redundancy, or repetition of schema details.

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?

The description conveys core purpose and filter categories, and the schema covers all parameter details. However, there is no output schema and the description omits operational details such as pagination semantics, time-range behavior, and what fields are returned for each event, leaving some important context for the agent to 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%, so the schema fully documents all 9 parameters with descriptions. The tool description only summarizes filter categories (time, country, port, vessel, event type) without adding meaning beyond the schema, which matches the baseline for high schema coverage.

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 uses a specific verb ('List') with a clear resource ('port events') and scope ('globally'), and enumerates the main filter categories: time, country, port, vessel, and event type. This clearly distinguishes it from sibling tools like get_port_events or search_port_events_by_vessel, which target a single port or vessel.

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 phrase 'globally' provides clear context that this tool is for cross-port event searches rather than port-specific or vessel-specific lookups. It does not explicitly name sibling alternatives or state when not to use it, but the global scope plus optional filters gives an agent enough context to select it appropriately.

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