evolute_charge

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

With no annotations present, the description carries the full behavioral burden. It usefully discloses that the result is empty when not charging, preventing misinterpretation of a no-active-session state. It does not mention auth, rate limits, or read-only semantics, but for a zero-parameter current-state getter this is sufficient.

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 two short sentences with no filler. The main resource is front-loaded, and the important conditional behavior ('Empty when not charging') is stated separately and clearly.

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 zero-parameter tool with an output schema available, the description covers the key edge case and return semantics. It is slightly terse about what 'current' refers to and does not cross-reference sibling tools, but nothing essential is missing for a simple read operation.

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 tool has zero parameters and the input schema is an empty object, so there is nothing for the description to add. The baseline for a parameterless tool is appropriate here.

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 identifies the resource ('current charge session') and the conditional empty state, which distinguishes it from siblings like evolute_vehicles or evolute_trips. It lacks an explicit verb such as 'retrieve' or 'list,' but the intent is unambiguous for a simple getter.

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 when the tool is relevant: use it to inspect the current charge session, knowing it will be empty when not charging. However, it does not explicitly contrast it with sibling tools such as evolute_status or state when not to use it.

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