are_due

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

Discloses the core behavior of checking due status. Without annotations, it should mention that this is a read-only operation and that invalid card IDs might cause errors. Currently adequate but not exhaustive.

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?

Single sentence with no wasted words. Information is front-loaded and easy to parse.

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 predicate tool with one parameter and an output schema, the description is mostly complete. Missing details about handling of missing or invalid IDs, but the output schema likely covers return format.

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?

Adds meaning by stating 'For each card ID', clarifying that the array parameter maps to individual checks. Schema coverage is 0%, so this explanation is valuable. Could specify that IDs must be integers.

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?

Clearly states the verb 'return' and the resource 'whether each card is due for review'. Distinguishes from sibling are_suspended by checking a different property.

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?

No guidance on when to use this tool versus alternatives like are_suspended or other card-status tools. The description assumes the agent knows the context.

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