energy_add_grid_consumption

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

Discloses a side effect (creating grid source if needed), which is beyond the bare parameters. No annotations, so description carries the burden. However, it does not mention what happens if the source already exists, any required permissions, or details about the consumption flow itself.

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?

Single sentence, front-loaded with action and resource. No redundant words. Efficiently conveys the core purpose and a key condition (creating source if needed).

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 existence of an output schema, return value info is not required. However, the description lacks details on parameter formats (e.g., entity ID patterns) and usage prerequisites. The simple nature keeps it adequate but not comprehensive.

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?

Input schema has 2 parameters with 0% description coverage. The description only hints at 'flow_from' but does not explicitly link to stat_energy_from or explain stat_cost. Missing parameter explanations force the agent to guess meaning.

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?

Clearly states the action ('Add'), resource ('grid consumption flow'), and context ('Energy Dashboard's grid source'). The condition 'creating the grid source if needed' adds specificity. Distinguishes from other energy_add_* tools by specifying 'grid consumption' and 'grid source'.

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 explicit guidance on when to use this tool vs alternatives like energy_add_battery_source or energy_add_solar_source. The description implies usage for grid consumption but doesn't exclude or compare against siblings, leaving the agent to infer selection.

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