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

The description adds useful behavioral context: it only considers ACTIVE schedules, defaulting to 30 days, and the free tier truncates results to the first 3 occurrences. However, since readOnlyHint is false and the description never explicitly states this is a read-only report, an agent cannot fully rely on its apparent list-only nature.

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 short, information-dense sentences. The core operation is front-loaded, the scope and returned fields are specified, and the free-tier limit is included compactly. There is no filler or redundancy.

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 one-optional-parameter tool with no output schema, the description supplies the essential return information (amount, invoice due date, total per currency) and the horizon/free-tier behavior. It lacks finer details like timezone handling or exact output field names, but those are minor given the simplicity of the tool.

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%: the `days` parameter description already documents the default, min/max range, and free-tier vs. Pro behavior. The tool description repeats the 30-day default and free-3 limit but adds no new parameter semantics, so it does not elevate beyond the schema baseline.

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 states a concrete operation: 'Table every occurrence of every ACTIVE schedule due in the next N days,' specifying the resource (active schedules' due occurrences), the default horizon, and the returned data (amount, invoice due date, total per currency). This clearly distinguishes it from sibling tools like schedule_get, schedule_list, and schedule_history, which focus on individual schedules or different views.

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 gives clear context for when to use it: when you need an aggregate view of upcoming due occurrences across all active schedules within a horizon. It does not explicitly name alternatives or state exclusions, so it stops short of a fully explicit routing guide, but the intended use is strongly implied.

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