maritime_get_hull_profile

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

No annotations provided, but description explains it's a retrieval operation returning hull profile data. Does not explicitly state idempotent/read-only, but is implied. Adds context on returned fields and purpose, though could mention no side effects.

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 clear sections: description, args, returns, tips. No redundant sentences, front-loaded with key info, efficiently covers all needed aspects.

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?

Despite no output schema or annotations, description covers purpose, parameters, return content, and usage tips. Domain-specific advice makes it complete for the tool's complexity.

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?

Input schema has no enums and 0% coverage. Description adds full parameter details: lists allowed ship_type values and output_mode options (json/text), exceeding schema info.

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?

Clearly states 'Get hydrodynamic hull profile for a VOC ship type' with specific fields listed. Distinguishes from sibling 'maritime_list_hull_profiles' which lists types, while this retrieves the profile.

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 tips: use with maritime_list_hull_profiles to see types, essential for drift modelling, notes retourschip as most common. Tells when to use and references sibling.

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