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

No annotations are provided, so the description carries full burden. It discloses important behavior: omitting zip_code returns statewide catalog rather than TDU-filtered buyable plans. It lists return data (rates, contract length, fees, signup requirements). Could mention if changes are destructive or require auth, but for a read operation it suffices.

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 front-loaded with purpose and usage, then details parameters. It's somewhat verbose but each sentence is informative. Minor trimming possible, but structure is logical and effective.

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 no output schema, the description adequately explains return values. Both parameters are covered, usage context is clear, and siblings are referenced for alternatives. The tool is fully contextualized for an agent to decide when and how to invoke it.

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 coverage is 100%, but the description adds significant meaning beyond the schema. It explains that zip_code is used for TDU filtering and that omitting it returns statewide results. It also clarifies provider_slug as an identifier. This value-add justifies a 5.

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 it retrieves 'plans, pricing, and terms for a specific Texas utility provider,' using specific verb ('Get') and resource. It distinguishes clearly from siblings like 'search_utility_providers' and 'compare_providers' by stating use cases.

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?

Provides explicit when-to-use context ('after search_utility_providers has narrowed the list') and includes example user queries. Also gives clear when-not-to-use guidance: 'Don't use this to discover providers (use search_utility_providers) or to compare across REPs (use compare_providers).'

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