list_external_debts_tool

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

Since no annotations are present, the description carries full responsibility for disclosing side effects. While 'List' implies a read-only operation, the description does not explicitly state that no data is modified, nor does it mention any potential changes to state or data. This lack of explicit transparency lowers the score.

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 and to the point: a single clear sentence followed by a short note. It avoids unnecessary details and is well-structured for quick understanding.

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?

The description covers the essential function and scope, and given the absence of parameters and output schema, it is nearly complete. However, the 'Plaid-only' note is unexplained and could leave the agent uncertain about platform constraints, slightly reducing completeness.

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 zero parameters, so schema coverage is 100% (vacuously). The description has no need to explain parameters. Per the rubric, with high schema coverage, the baseline score is 3.

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's purpose with a specific verb ('List') and a precise resource ('external (non-Plaid-linked) debt'). The qualifier 'external (non-Plaid-linked)' effectively distinguishes it from sibling tools like get_liabilities_tool or summarize_debt_tool.

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 the core function but offers no explicit guidance on when to choose this tool over alternatives. The 'Plaid-only' note is ambiguous and could be interpreted as a restriction, but it is not explained as a usage condition. No alternative actions or decision heuristics are mentioned.

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