get_battery_soc

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 says 'Get', implying a read-only operation, but does not mention any authentication requirements, error behavior, or side effects. No additional context is provided beyond the verb.

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 short sentence with no unnecessary words. It is front-loaded and gets straight to the point. However, it is so terse that it veers toward under-specification, though not enough to lower the score significantly.

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 simple tool with one parameter, the description is incomplete. It does not explain the purpose or possible values of the 'instance' parameter, nor does it provide context on when to use this tool among the sibling getters. The output schema exists but is not referenced 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 input schema has one parameter 'instance' with no description, and the schema description coverage is 0%. The description does not mention the parameter at all, leaving the agent without any understanding of what 'instance' refers to or how to use it.

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 'Get battery state of charge' uses a specific verb ('Get') and resource ('battery state of charge'), clearly distinguishing it from siblings like get_pv_power and get_grid_status. It precisely identifies the tool's function.

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?

There is no guidance on when to use this tool versus alternatives. The description simply states what it does without mentioning context, prerequisites, or exclusions. It does not name any sibling tool or explain when this read is appropriate.

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