Import Transactions

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

Annotations indicate readOnlyHint=false, consistent with the 'trigger' action implying a write operation. The description adds useful context by specifying '[1 API call]' (implying a single operation) and that it imports from 'linked financial institutions', which aren't covered by annotations. However, it lacks details on side effects (e.g., data overwriting), authentication needs, or rate limits.

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—a single sentence with no wasted words. It's front-loaded with the key action and resource, and the bracketed '[1 API call]' efficiently conveys operational context without verbosity.

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 complexity (a write operation with no output schema), the description is minimally adequate. It covers the core action and source but lacks details on outcomes (e.g., what happens after triggering), error handling, or integration with sibling tools. With annotations providing only readOnlyHint, more behavioral context would improve 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?

Schema description coverage is 100%, so the schema fully documents the single parameter 'budget_id'. The description adds no additional parameter information beyond what's in the schema, such as explaining why a budget ID is needed or how 'last-used' works. This meets the baseline for high schema coverage.

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 action ('Trigger an import') and resource ('transactions from linked financial institutions'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'create_transactions' or 'list_transactions', which handle different aspects of transaction management.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing linked institutions), timing considerations, or how it relates to sibling tools like 'create_transactions' for manual entry or 'list_transactions' for viewing imported data.

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