Marlo MCP

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action ('list all exteral loans') without any details on permissions required, rate limits, pagination, sorting, or what the output includes (e.g., loan IDs, amounts, statuses). This is inadequate for a tool with zero annotation coverage.

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, misspelled phrase ('list all exteral loans') that is under-specified rather than concise. It lacks structure, such as front-loading key details or providing any additional context, making it inefficient despite its brevity.

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 no annotations, no output schema, and a simple listing function, the description is incomplete. It fails to explain what 'list' entails (e.g., returns a summary vs. full details, potential filters, or format), leaving gaps in understanding the tool's behavior and output.

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 tool has 0 parameters with 100% schema description coverage, meaning the schema fully documents the lack of inputs. The description does not add parameter information, which is unnecessary here. A baseline of 4 is appropriate as no parameters exist, and the schema handles this completely.

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 'list all exteral loans' restates the tool name with a spelling error ('exteral' instead of 'external'), making it essentially tautological. It does specify a verb ('list') and resource ('external loans'), but fails to differentiate from sibling tools like 'get_external_loan_details' or 'list_all_marlo_loans', which suggests similar listing functions for related resources.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it refer to sibling tools like 'get_external_loan_details' for detailed views or 'list_all_marlo_loans' for related loan types. This leaves the agent with no usage direction.

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