grid_intelligence

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

No annotations provided. Description says the tool gives 'real-time' data but does not mention update frequency, rate limits, or other constraints. For a read-only data retrieval tool, it is adequate but not rich.

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?

Four sentences, front-loaded with purpose and then usage/parameter guidance. No extraneous words; every sentence 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?

Given a single optional parameter and an existing output schema, the description covers the tool's purpose, use cases, and parameter format completely.

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?

Despite 0% schema description coverage, the description fully explains the 'region' parameter by listing all valid region codes (CISO, ERCO, etc.), adding significant meaning beyond the schema's plain string type.

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?

Description clearly states it provides US electricity grid intelligence (real-time demand, generation mix, grid stress signals) and specifies use cases like optimizing industrial operations, EV charging, and compute workloads. This differentiates it from sibling tools like energy_markets.

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?

Describes explicit use cases and provides region codes with guidance on leaving empty for all regions. Does not explicitly mention when not to use or alternatives, but the context is clear.

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