get_upcoming_transactions

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

The description reveals meaningful behavioral details beyond the schema: returns a summary line 'Showing X-Y of Z upcoming transactions', sorts soonest first, and documents key behaviors like limit=0 returning count only and verbose mode changing output format. No contradictions with annotations (none provided).

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?

Well-structured with a clear lead framing, a 'what bills are coming up?' hook, then a compact Args section. Every line serves a purpose—no filler, no repetition of schema defaults that aren't useful.

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 read-only paginated listing tool, the description is thorough. An output schema exists so return value documentation burden is reduced. Could mention what happens with no scheduled transactions, but given good annotations-free disclosure of format and paging, this is very solid coverage.

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%, so the description carries the full burden of explaining parameters. It describes each arg's purpose and default: days (look-ahead window), verbose (full JSON vs compact line), limit (page size with count-only special case), offset (0-indexed pagination). This is genuinely additive beyond the bare schema.

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 this lists scheduled/upcoming transactions due within a time window, with the specific 'what bills are coming up?' use case. It distinguishes from siblings like list_transactions and search_transactions by focusing specifically on scheduled/recurring transactions due soon.

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 makes the use case explicit ('what bills are coming up?') and explains pagination and the leading summary line format. It doesn't explicitly contrast with alternatives like list_scheduled_transactions or create_transaction_from_scheduled, but the purpose framing gives clear context for when to use it.

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