get_state_energy_profileState energy profile from EIA: total consumption, production, electricity generation, renewable percentage, and top energy sources. Returns production mix and trends.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | Two-letter state code (e.g., TX) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat safety. It adds context about the data source (EIA) and specific data fields, but does not disclose behavioral traits such as response format, pagination, or rate limits.
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, no wasted wording. Front-loaded with source and purpose, then lists contents and returns. Efficient and clear.
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?
For a simple read-only tool with one parameter and no output schema, the description provides a good overview. It could mention the likely JSON output format or include an example, but it is adequate for an agent to understand what to expect.
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?
Schema description coverage is 100% (one parameter with clear description). The tool description adds no additional meaning beyond what the schema already provides for the 'state' parameter.
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 explicitly states the tool provides a state energy profile from the EIA, listing specific data categories (total consumption, production, electricity generation, renewable percentage, top energy sources). It clearly distinguishes from sibling tools like get_state_climate_profile by focusing on energy metrics.
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 use for state energy data but does not explicitly state when to use this tool versus alternatives. No when-not or exclusion criteria are provided, although the context of sibling tools suggests it is the primary tool for energy profiles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, specific purpose with detailed descriptions that differentiate them. Prefix patterns like get_district_, search_, analyze_, get_, etc., help an agent easily identify the correct tool for a task.
All tool names use a consistent verb_noun or verb_noun_noun pattern with underscores. The naming convention is uniform across the entire set, with no mixing of styles or ambiguous verbs.
With 47 tools, the count is high but justified by the broad scope of civic data analysis. While some agents might find the sheer number overwhelming, the tools are organized into clear categories (district profiles, searches, analyses) that make navigation feasible.
The toolset covers an impressively wide range of domains: legislation, representatives, districts, voting, committees, campaign finance, lobbying, federal spending, regulations, environment, energy, healthcare, housing, disaster, banking, consumer complaints, crime, vehicles, and more. There are no obvious missing operations for a civic data platform.