sync_vouchers_to_sql

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

The description clearly explains the read-only nature (pulling data), the in-memory session cache behavior, and the implications of session scope and company changes. It adds context beyond the readOnlyHint annotation, such as cache lifecycle and timeout handling.

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 excessively verbose and repetitive, with multiple warnings and instructions (e.g., 'call this once per chunk', 'pick a chunk size that won't time out', repeated mentions of session/company scope). It could be significantly condensed while retaining essential 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?

Despite verbosity, the description is very complete: it explains the tool's purpose, usage patterns, alternatives, constraints, and interaction with session state. It covers all key aspects needed for correct usage, including edge cases like company switches and timeout management.

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?

The input schema already covers 100% of parameters (from and to) with format descriptions. The description adds context about chunking and timeouts based on date range, which is useful for effective parameter selection.

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 explicitly states it pulls voucher headers for a date range into a SQL cache for querying, distinguishing it from sibling tools like get_vouchers and sync_voucher_items_to_sql. The verb 'pull' and resource 'voucher headers' are clear and specific.

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 explicit usage guidance: when to use it for aggregation/reporting, how to chunk data to avoid timeouts, when to re-sync after a company change, and how it differs from alternatives like get_ledger_vouchers and sync_voucher_items_to_sql. It also states the safe re-run behavior.

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