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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description adds that results carry codes and current contents plus the underlying GET endpoint, but says nothing about pagination behavior, result caps, or permissions beyond what the annotations cover.

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?

Three tight sentences, front-loaded with what the tool returns and followed by the filter surface. The middle sentence largely echoes schema fields, which is mild redundancy rather than bloat.

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?

For a read-only list tool with full schema coverage and no output schema, the description supplies the key return context (vessels with codes and current contents) and the endpoint. The only gaps are the paging envelope and total counts, which the schema's next_offset hint partially covers.

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%, so every one of the eight parameters is already documented in the schema, including paging via limit/offset and the winery_id pattern. The description restates five of the filters and omits limit/offset entirely, adding no syntax or semantics beyond the schema; 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 gives a specific verb and resource ("List tanks, barrels and other vessels") and states what comes back (codes and current contents). It is clear, but it does not differentiate itself from the close sibling innovint_list_vessels_at_point_in_time, leaving the agent to infer that this one is current-state only.

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 filter list implies how the tool is used (narrow by search term, code, id, lot, archived state), but there is no explicit when-to-use or when-not-to-use guidance. In particular, no signal about choosing this over innovint_list_vessels_at_point_in_time for historical snapshots.

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