get_battery_levels

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

Without annotations, the description carries full burden. It states the condition for inclusion (battery levels at or below threshold), but it does not specify edge cases (e.g., threshold bounds, inclusivity) or whether the result includes only devices with battery data. Nonetheless, the core behavior is clear and non-destructive.

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: one for the overall purpose and one for the single parameter. No redundant or extraneous text.

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?

Given the tool's simplicity (one parameter, output schema present), the description covers the essential use case. The existence of an output schema means return values do not need to be explained in the description.

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 description restates the parameter name, type, and default from the schema without adding new semantic information (e.g., range of valid values, that it is a percentage). Since schema coverage is 0%, the description provides minimal compensation.

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 ('Get'), the resource ('devices with battery levels'), and the filtering condition ('at or below the specified threshold'). It distinguishes from siblings like 'get_all_devices' by specifying the filtering criterion.

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 when needing devices with low battery, but it does not provide alternatives or exclusion criteria. For example, it doesn't mention when to use 'get_all_devices' instead or that only devices with battery info are returned.

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