maritime_list_hull_profiles

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

Discloses return format options (JSON or text) and the nature of output (VOC ship type identifiers). With no annotations, this covers essential behavior for a simple list tool.

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?

Well-structured with main purpose, args, returns, and tips. Front-loaded and efficient, though the Arg/Return sections could be slightly tighter.

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?

Complete for a simple list tool with one optional parameter: explains purpose, usage, return details, and provides common examples. Does not need output schema as return is self-explanatory.

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?

Despite 0% schema_description_coverage, the description explains the output_mode parameter's values and default, compensating fully for the missing schema documentation.

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 lists available ship types with hull profiles, using specific verbs ('List', 'Returns') and distinguishes itself from sibling maritime_get_hull_profile by explicitly recommending prior use.

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?

Provides explicit instruction to use before calling maritime_get_hull_profile and lists common ship types. However, does not mention when not to use or alternative tools beyond the one get function.

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