importTransactions

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

With no annotations provided, the description carries the behavioral disclosure burden. It states the action (imports transactions), the scope (all linked accounts), that it initiates the import, and that the response contains imported transaction IDs. It does not discuss idempotency, failure modes, or side effects, but the core behavior is well disclosed.

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 compact and front-loaded with the main action. The second sentence adds context about linked accounts but partially repeats the first sentence ('this endpoint initiates that import'). Still, there is no filler and the length is appropriate.

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 single-parameter endpoint with an output schema, the description covers the action, the scope, and the response contents. It could mention behavior with no available transactions or repeated calls, but as it stands it supplies what an agent needs to invoke the tool correctly.

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 100%, so the schema already fully documents plan_id, including special values like 'last-used' and 'default'. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Imports available transactions on all linked accounts for the given plan.' This clearly distinguishes the tool as the automatic-import action, not a manual create or read operation. The UI analogy ('equivalent of clicking Import') further anchors exactly what the endpoint performs.

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?

It provides clear context for when to use the tool: when there are linked accounts and you want to import available transactions from the financial institution. It does not, however, explicitly mention alternatives or when-not-to-use cases, such as distinguishing from createTransaction for manual entry.

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