list_ferries

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

With no annotations, the description carries the behavior disclosure burden. It clearly signals a read-only enumeration and scopes the result to 'all known' ferries, but it does not mention output shape, data freshness, or whether this is a live or cached view. That is acceptable but minimal.

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 with no filler. It communicates the essential scope and operation efficiently.

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?

For a parameterless list operation, this is mostly complete: it identifies the resource, scope, and that details are returned. The main gap is the absence of explicit differentiation from the tracking siblings and lack of detail on what 'details' specifically includes, but the low complexity keeps this adequate.

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 has zero parameters and the schema coverage is trivially 100%, so there is no parameter documentation burden. Baseline 4 applies because no parameters need semantic explanation.

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 states a clear verb and resource: list all Boston Harbor commuter ferries with their details. It is unambiguous about the operation, though it does not explicitly differentiate itself from track_all_ferries.

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 description implies this tool is for retrieving a static catalog of all ferries, but it provides no explicit guidance on when to choose it over track_ferry, track_all_ferries, or get_ferry_routes. Usage context is only inferred from the word 'list'.

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