What falls due soon

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

No annotations are provided, so the description carries the full burden. It does disclose the free-tier truncation behavior and the output fields, which is useful. It does not mention read-only status, ordering, timezone, or whether already-overdue items are included, so transparency is partial.

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, front-loaded with the core output, and no filler. The free-tier limitation is important context and is kept brief, though it overlaps with the schema description.

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 simple one-parameter read tool with no output schema, the description covers the essential return values and the key free-tier constraint. It is complete enough for an agent to call it correctly, though details like ordering or grouping of currencies are left implicit.

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 100% and the days parameter description already covers default, horizon, and free/Pro behavior. The tool description adds little beyond restating 'next N days' and the free-tier first-3 occurrences behavior, so it does not meaningfully expand on the 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 what the tool returns: a table of schedule occurrences due in the next N days, with amount per occurrence and total per currency. It is distinguishable from siblings like schedule_list or schedule_get by its focus on upcoming due occurrences, though it does not explicitly name an alternative.

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 'next N days' and 'falling due' language implies this is for due-date lookahead queries, but there is no explicit guidance about when to choose this over schedule_list, schedule_get, or schedule_history. Usage context is implied rather than stated.

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