interconnection-queue-tracker

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

With no annotations, the description carries the transparency burden and provides useful behavioral context: it is keyless, reads live from official government sources, and normalizes/tracks deltas. It does not mention potential side effects like internal KV snapshot writes or rate limits, but the read-oriented framing is reasonably 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 compact and front-loaded with the core function, followed by audience, auth, and data-source context. The store link is a useful addition and 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?

The description covers domain, scope, audience, auth, and data source, and the schema supplies exhaustive parameter detail. There is no output schema and the description does not fully specify the response structure, but the normalized-queue/delta concept is enough to orient an agent reasonably well.

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%, and the input schema already provides detailed semantics for all 6 parameters. The description adds overall domain context but no parameter-level detail beyond what the schema already contains, so the baseline 3 applies.

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 uses specific verbs ('Normalize', 'track') and names the exact resource ('US ISO/RTO generator interconnection queues') across all 7 ISOs. It clearly distinguishes the tool from sibling data tools by domain and functionality.

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 audience and context are clear ('renewables developers, land agents, energy consultants'; live US ISO queue monitoring and deltas), making the intended use obvious. It does not explicitly name alternatives or state when not to use it, so it falls 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.