charger.read_slots

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

The description provides some behavioral info (slot is zero-based, range 0..3), but lacks disclosure on whether the operation is read-only, requires authorization, or has side effects. With no annotations, the description carries the full burden and is only partially adequate.

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 concise sentences with no fluff. Information is front-loaded and each word adds value. Ideal for quick parsing.

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 one-parameter tool with no output schema or annotations, the description is mostly adequate but lacks information about return values or possible errors. It leaves some gaps for the agent to infer.

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 0% description coverage, so the description must compensate. It explains the parameter 'slot' is zero-based with range 0..3, adding meaning beyond the schema's min/max constraints. However, it does not explain the behavior when omitted (all slots) or the output format.

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 tool reads slot statuses and specifies the slot range. It distinguishes from sibling tools like 'charger.get_status' by focusing on individual slot statuses, but does not explicitly differentiate.

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 'charger.get_status'. The description only states what it does, leaving the agent to infer usage context.

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