bookmind.fetch_transactions

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

With no annotations, the description must disclose behavioral traits. It mentions caching in SQLite, which is a key trait. However, it does not state whether the operation is read-only, whether authentication is required, or rate limits. It also does not describe what happens if the fetch fails.

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?

Two sentences, each adding value: first covers purpose and output, second covers caching behavior. No redundant or extraneous information.

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 no output schema, the description explains the output format as 'normalized JSON array' and notes compatibility with other tools. Caching behavior is described. However, it lacks detail on error handling or the structure of the returned data. For a tool with 6 parameters, it is reasonably 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?

Schema coverage is 83%, so the schema already explains most parameters. The description adds minimal additional meaning beyond 'returns cached data only' for the 'fetch' parameter. No new syntax or format details are provided for parameters like start_date and end_date.

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 (fetch), resource (transactions), and scope (date range from QuickBooks Online). It also specifies the output format as a normalized JSON array compatible with other tools, which gives context. However, it does not explicitly distinguish from sibling tools like 'sync_to_qbo' or 'chase_email'.

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 implies usage when data is needed for downstream tools (categorize, reconcile, etc.) and mentions caching, which suggests repeated use. But it does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives among siblings.

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