trybiut_movements_list

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

With no annotations, the description carries the behavioral burden. It discloses that login is required and uses the read verb 'List', which implies a read-only operation. It does not explicitly state that no side effects occur, nor does it describe output format, pagination, or limit behavior, leaving some important traits implicit.

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 only two short sentences. The core operation and scope are front-loaded, and 'Requires login' is a concise, necessary precondition. There is no filler or redundant wording.

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?

For a simple list operation with one optional parameter, the description is nearly sufficient: an agent can call it with no arguments and know it returns a user's movements. However, with no output schema and no mention of returned fields or how 'limit' affects results, some contextual detail is missing.

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% for the single 'limit' parameter, and the description does not mention limit, pagination, or how many movements are returned. The schema itself provides type, min, max, and default, which helps, but the description fails to compensate for the low coverage as required.

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 states a specific verb and resource: 'List bank/income-expense movements of the logged-in user.' This clearly identifies what the tool does and who it applies to. However, it does not explicitly differentiate itself from siblings like invoices_list or tax_history, leaving that distinction to the resource name.

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 tool's purpose implies it should be used when an agent needs the logged-in user's bank/income-expense movements, and 'Requires login' signals a prerequisite. There is no explicit when-not-to-use guidance or naming of alternative tools, so usage context is only implied rather than stated.

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