ercot_prices

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

With readOnlyHint=true in annotations, the read-only safety is already known. The description adds domain context and common settlement point examples, which is helpful. However, the claim of 'real-time' seems at odds with the delivery_date_from/to parameters in the schema, implying historical data is also available—this is a slight behavioral inconsistency. No additional details on pagination, default scope, or return format are provided beyond annotations.

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 two short paragraphs: one high-definition sentence about what the tool does, and one compact list of common settlement points. Every sentence earns its place, no filler, and the most important information is front-loaded.

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 simple read-only query tool with full schema coverage and no output schema, the description provides adequate context. It explains the domain, gives example parameters, and the annotations confirm safety. The main gap is not describing what the returned data looks like (since there's no output schema) and not clarifying the historical/real-time tension, but these are minor for a tool like this.

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%, so all five parameters are already documented. The description adds value by enumerating common settlement point values, directly supplementing the settlement_point parameter. It also clarifies the geographic scope (Texas) and data type (wholesale electricity prices). Minor point: 'real-time' could confuse the default-date behavior, but that's a description trait, not a param semantic.

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 'Get Texas (ERCOT) settlement point prices' with a specific verb and resource, and further defines the domain as 'real-time wholesale electricity prices at specific nodes, zones, or hubs.' This distinguishes it from sibling tools like ercot_grid_conditions, and gives concrete examples of settlement points (HB_HOUSTON, HB_NORTH, etc.), removing ambiguity.

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 provides clear context: this tool is for Texas ERCOT settlement point prices. It doesn't explicitly name alternatives or exclusions, but the domain-specific examples and the resource type make it evident when to use it. The gap is lack of explicit comparison to similar tools (e.g., ercot_grid_conditions), so it stops short of a 5.

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