get_vessel_positions_batch

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

No annotations are provided, so the description carries the full burden for behavioral transparency. It only states what the tool does without disclosing details such as pagination (nextToken), default time ranges, limits on batch size, or potential rate limits. This is a significant gap for a batch operation.

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, concise sentence that is front-loaded with the core purpose. It avoids redundancy and is well-structured, every word adds value.

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 batch nature and lack of output schema, the description provides only the bare minimum. It does not explain that the response will contain positions for each requested vessel or mention pagination, which are relevant for a batch API. The schema partially compensates, but the description could be more complete.

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 already provides descriptions for all parameters (100% coverage), so the baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., 'by MMSI or IMO numbers' is already in the ids parameter description). No contradictions or additional insights.

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's purpose: 'Get positions for multiple vessels at once by MMSI or IMO numbers'. It specifies the action (get positions), the resource (multiple vessels), and the identifier types, which distinguishes it from sibling tools like get_vessel_position (single vessel) and search_vessels.

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 usage for batch position retrieval ('multiple vessels at once'), which contrasts with single-vessel tools in the sibling list. However, it does not explicitly state when not to use this tool or reference alternatives. The context is clear but not prescriptive.

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