wsdot_ferry_schedule

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

The annotation readOnlyHint=true already indicates safe read-only operation. The description adds context about the returned data fields but does not disclose potential limitations such as schedule availability ranges, error conditions, or whether all routes are included. It is consistent with annotations, so no contradiction.

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 two sentences, front-loaded with the main purpose and a concise list of return content. No wasted words.

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?

Given the tool's simplicity (one required parameter), the description covers the essential information: what it gets and what it returns. While there is no output schema, the description summarizes the response structure adequately for an agent to invoke and interpret the result.

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 input schema has 100% coverage for the single 'date' parameter, including format and example. The description only mentions 'specific date' and does not add extra semantics beyond the schema, so 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 states the tool retrieves Washington State Ferries sailing schedules for a specific date, with a specific verb ('Get') and resource ('sailing schedules'). It distinguishes from siblings like wsdot_ferry_vessels and wsdot_ferry_terminals by focusing on schedules and listing return contents (route descriptions, crossing times, individual sailing times).

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 gives clear context: use this tool when you need schedules for a specific date, and it indicates what is returned. However, it does not explicitly name alternative tools for related ferry data (e.g., vessels or terminals), so it lacks explicit exclusion guidance.

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