get_vessel_emissions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get emissions data,' which implies a read operation, but does not disclose pagination behavior (nextToken), default identifier type, rate limits, or any other behavioral traits. The description adds no context beyond the action itself.

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 with a clear verb and purpose, front-loaded with 'Get emissions data.' No wasted words, though it could include sibling differentiation or usage hints without becoming verbose.

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?

With no output schema and no annotations, the description is adequate but minimal. It does not mention pagination tokens, identifier defaults, or how this tool compares to list_emissions. For a tool with four parameters and many siblings, richer context would help, but the schema already covers parameter meanings.

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?

Schema description coverage is 100% (all four parameters have descriptions), so the baseline is 3. The description does not add parameter-level meaning beyond the schema; it mentions data fields (CO2, fuel consumption) but not how parameters affect the output. No credit is needed beyond the schema's existing coverage.

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'), the resource ('emissions data for a vessel'), and the data scope ('CO2, fuel consumption'). This distinguishes it from sibling vessel tools like get_vessel_position and get_vessel_eta, and the 'for a vessel' qualifier separates it from list_emissions.

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 given about when to use this tool versus alternatives. The sibling list_emissions likely provides fleet-level emissions data, but the description does not mention trade-offs or exclusions. There is no 'when not to use' or reference to other tools.

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