Batteries Due Tool

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

No annotations are provided, so the description must carry the full burden. It only states the basic function ('Return batteries due') and implies a read operation via 'Return', but does not disclose any behavioral details such as sorting, pagination, inclusion/exclusion of overdue batteries, or any side effects. It adds little beyond the tool name.

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 a single, concise sentence with no redundant words. It is front-loaded with the primary purpose and immediately communicates the core functionality.

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 tool with one optional parameter and an output schema (not shown), the description is minimally adequate. It does not mention edge cases (e.g., whether overdue batteries are included) or clarify the meaning of 'due', but given the low complexity, it is not severely incomplete.

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 schema has a single optional parameter 'days' with a default of 7, and schema description coverage is 0%. The description mentions 'given number of days', which clarifies the parameter's meaning but does not explain the default behavior or edge cases (e.g., days=0). It provides minimal added value over 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 the action ('Return batteries due') and the temporal scope ('within the next given number of days'), distinguishing it from the sibling 'batteries_overdue_tool' (past due) and 'batteries_list_tool' (all batteries). However, it does not explicitly name alternatives or contrast with them, leaving some ambiguity for an agent.

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 is provided on when to use this tool versus its siblings like 'batteries_overdue_tool' or 'batteries_list_tool'. The description only states what it does, not when it should be selected or what conditions exclude it.

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