set_grid_export_limit

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

With no annotations, the description carries the full burden. It discloses the valid range (0–10000) and that 0 disables export, but fails to mention whether the change is persistent, requires permissions, or what the response is. Minimal behavioral context.

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 sentences plus parameter detail, no wasted words. Information is front-loaded and efficiently communicated.

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?

The description is adequate for a simple 1-parameter setter, but lacks details like confirmation of success, persistence, or side effects. The presence of an output schema (not shown) may mitigate, but the text remains minimal.

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 parameter limit_watts lacks schema description (0% coverage). The user description adds essential semantics: 'Power limit in watts (0–10000). Use 0 to disable export.' This fully compensates for the schema gap.

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 action: 'Set the maximum power the inverter may export to the grid.' It specifies the verb (set) and resource (grid export limit), and distinguishes from the sibling get_grid_export_limit.

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 usage for adjusting the export limit, and the sibling tools provide context (e.g., get_grid_export_limit for reading). However, it lacks explicit guidance on when not to use or prerequisites.

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