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

No annotations provided, so description carries the burden. It mentions public-domain records and price per row, but does not explicitly state read-only behavior, rate limits, or data freshness. The behavior is implied as a search, which is acceptable but not fully transparent.

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 concise at a few sentences, starting with a guiding question and covering purpose, returns, audience, source, and pricing. Some marketing language (target audience) is present but not excessive; overall efficient.

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?

Despite 9 parameters and no output schema, the description covers the main purpose and return fields. It misses details like pagination behavior (though limit/offset exist) and error handling. The price mention adds value, but overall completeness is adequate but not comprehensive.

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% with descriptions for all 9 parameters. The tool description lists the searchable fields but adds no new meaning beyond the schema. It does provide useful output field context, but that does not enhance input parameter understanding.

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 it searches the PHMSA pipeline operator roster by specific fields (name, ID, state, etc.) and returns key details. It distinguishes from sibling tools like phmsa_incidents_search by focusing on operators and market context.

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 finding operators in a market via the question 'Which pipeline operators are in a market?', but lacks explicit guidance on when not to use or how it compares to other PHMSA tools (e.g., incidents search).

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