ship_fishing

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

No annotations provided; the description discloses the tool's purpose and outputs but omits behavioral traits such as data freshness, required permissions, or performance considerations. It does not contradict any annotation.

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 efficiently conveys the tool's core functionality without extraneous 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 absence of an output schema, the description name-drops key outputs (fishing hours, vessel count, top flag states), which is helpful. However, it lacks details on return format or pagination, but the tool is a straightforward analytical query.

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?

All 6 parameters are fully described in the schema (100% coverage), and the description adds context that the tool analyzes an area over a date range, but does not provide additional meaning beyond what the schema already conveys.

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 analyzes fishing activity (specific verb-resource pair) and lists the outputs (fishing hours, vessel count, top flag states). It distinguishes from siblings like ship_track or ship_search, which focus on individual vessels or positions.

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 when to use (for aggregated fishing analysis) but does not explicitly state when not to use or mention alternatives among sibling tools like ship_area or ship_dark. More guidance would help differentiate.

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