simba_list_movements_by_src

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a list operation, implying read-only behavior, but doesn't mention pagination details (implied by parameters), rate limits, authentication needs, or what the output contains (though an output schema exists). The description adds minimal behavioral context beyond the basic action.

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, efficient sentence with zero waste. It's appropriately sized for a simple list tool, though this conciseness comes at the cost of detail. The structure is front-loaded with the core action, making it easy to scan.

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 moderate complexity (3 parameters, 1 required) and the presence of an output schema (which handles return values), the description is minimally complete but lacks depth. It covers the basic purpose but misses parameter explanations, usage context, and behavioral details. With no annotations and low schema coverage, it should do more to compensate, but the output schema reduces the burden slightly.

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?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description only mentions 'src_id' without explaining what it is (e.g., source ID, account ID) or the meaning of 'movimentacoes'. It doesn't address the pagination parameters 'pagina' and 'itens_por_pagina' at all, leaving them undocumented. The description adds very little semantic value beyond naming one parameter.

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 'Lista movimentacoes do SIMBA por src_id' clearly states the action (list) and resource (movements from SIMBA), but it's vague about what 'movimentacoes' specifically means (transactions, transfers, activities?) and doesn't differentiate from sibling tools like 'simba_list_accounts' or 'simba_list_movements_by_person_and_file'. The purpose is understandable but lacks specificity.

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 doesn't mention prerequisites, context, or exclusions, and it doesn't reference sibling tools like 'simba_list_movements_by_person_and_file' for comparison. Usage is implied only by the parameter 'src_id', but no explicit guidelines are given.

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