get_accounts

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

No annotations are provided, so the description carries the full burden. It only states 'List all user bank accounts' without disclosing any behavioral details such as authentication requirements, consent dependencies, pagination, or error behavior. This is a significant gap for a tool that likely requires an authorized connection.

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 one short sentence, making it extremely succinct and front-loaded. It earns its place by stating the core function, though it lacks additional structure (e.g., usage examples) that could be helpful.

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 tool's simplicity, the description is mostly complete, but it fails to differentiate from the sibling tool 'list_accounts'. There are no annotations to compensate for the missing usage context, and the tool appears to be one of two similar listing tools, so the description is not fully complete.

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, and schema description coverage is 100% vacuously. Per the rubric, a 0-parameter tool gets a baseline of 4, and the description appropriately confirms the tool takes no filters.

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 all user bank accounts, using a specific verb and resource. However, it does not distinguish between this tool and the sibling tool 'list_accounts', which appears to have the same purpose.

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 alternative tools. The description is a single statement with no context, exclusions, or recommended use cases.

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