get_vessel_casualties

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states that records are retrieved, but does not disclose pagination behavior, read-only nature, potential response structure, or any side effects. The description adds minimal value beyond the name.

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, concise and front-loaded. There is zero wasted text or redundancy. It is appropriately minimal, which is a strength given the low complexity of the tool.

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 lacks necessary context for a tool with no output schema and no annotations. It does not explain what casualty records include, the return format, or any specific behavioral aspects. Given the complexity (4 parameters, pagination), a richer description is warranted to make the tool fully usable without external documentation.

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 description does not add any parameter information beyond the schema. Schema coverage is 100%, with clear descriptions for limit, idType, vesselId, and nextToken. The phrase 'for a vessel' corresponds to vesselId, but the description adds nothing extra, so the baseline 3 for high schema coverage 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 action (Get) and the resource (marine casualty records) with a scope (for a vessel). It is distinct from sibling tools like get_vessel_position or get_vessel_emissions, as the resource type is unique. However, it lacks specificity on what 'casualty records' entails, so it doesn't fully distinguish edge cases.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any prerequisites, limitations, or alternatives. The one-line description offers no context for selection among the many sibling vessel-related tools.

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