Marlo MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers no information. It does not indicate whether this is a read-only or mutative operation, what the search returns, any rate limits, authentication requirements, or other behavioral traits, making it inadequate for a tool with unknown behavior.

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 extremely concise with only three words, 'Search multiple ports', which is front-loaded and wastes no space. However, this conciseness comes at the cost of under-specification, but structurally, it is efficient.

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 lack of annotations, 0% schema coverage, no output schema, and a single parameter, the description is incomplete. It does not provide enough context for an agent to understand the tool's purpose, usage, behavior, or parameters, making it insufficient for effective tool invocation.

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 schema description coverage is 0%, and the description does not compensate by explaining the 'port_names' parameter. It fails to clarify what port names are (e.g., identifiers, codes), their format, or how the search operates with them, leaving the parameter undocumented and unclear.

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 'Search multiple ports' restates the tool name 'search_ports' with minimal elaboration, making it tautological. It lacks specificity about what 'search' entails (e.g., filtering, retrieving details) or what 'ports' refers to in this context, failing to distinguish it from sibling tools like 'voyage_port_disbursements' or provide clear verb+resource details.

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 provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or comparisons to sibling tools (e.g., 'get_vessels' or 'search_cargos'), leaving the agent with no usage instructions.

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