get_grid_status

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

No annotations are provided, and the description adds no behavioral context. It does not disclose whether the operation is read-only, any side effects, error conditions, or data source specifics. The description simply restates the tool's function without adding transparency.

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, efficient sentence that immediately states the core purpose. It is concise and front-loaded, though it could include more detail; however, for a simple getter, this level of brevity is acceptable and every word earns its place.

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?

While the tool is simple with one optional parameter and an output schema, the description leaves out critical context about the meaning of 'grid/AC status' and the 'instance' parameter. It also lacks usage guidance or potential caveats, making it incomplete for reliable agent invocation.

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' (integer, default 0), but the description does not mention or explain it. With 0% schema description coverage, the description fails to clarify the parameter's meaning or usage, leaving the agent to infer from the schema alone.

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 grid/AC status' uses a specific verb ('Get') and resource ('grid/AC status'), clearly indicating the tool's primary function. It is distinguishable from sibling tools like get_battery_soc and get_pv_power by the resource type, though it does not explicitly elaborate on what 'status' encompasses.

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 usage guidance is provided. There is no mention of when to use this tool versus alternatives, prerequisites, or exclusions. The usage context is only implied by the tool's name and description.

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