Batteries Overdue Tool

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states what is returned, not how the results are ordered, whether the list is paginated, or what fields are included. The meaning of 'overdue' is left undefined. This minimal detail is insufficient for a tool that relies solely on its description.

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, direct sentence with no superfluous words. It is perfectly concise and front-loads the core action and target.

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 tool with no parameters and a simple list-returning purpose, the description is nearly complete. Since an output schema is present, return format details are not required. The only minor omission is clarifying the threshold for 'overdue,' but the overall context is adequate for a straightforward query 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?

There are no parameters, so the schema provides complete coverage. The description adds no parameter information because none exist, but this is not a gap. The baseline of 4 for zero parameters is appropriate.

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') and the specific resource ('batteries that are already overdue for charging'). It distinguishes itself from siblings like 'batteries_due_tool' by emphasizing the 'already overdue' condition, making the purpose unambiguous.

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 implies usage for retrieving overdue batteries but does not explicitly state when to prefer this over the similar 'batteries_due_tool' or other battery list tools. There is no mention of exclusions or alternatives, leaving the agent to infer the context from the tool name.

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