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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive intent. The description adds that the data is a real-time snapshot of currently constraining flowgates and facility limits, with shadow prices expressed in $/MWh of relief. No contradiction with 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 three tightly written sentences: what the tool returns, why that matters, and example user queries. Every sentence earns its place and there is no filler or repetition of annotation or schema details.

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 read-only tool with one optional parameter, a fully documented enum, and no output schema, the description provides sufficient context: the data content, units, and use cases. An agent has everything needed to decide when to invoke it and what to expect back.

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 single optional 'kind' parameter is already fully documented with enum values and descriptions. The description aligns with the default 'transmission' behavior but does not add new meaning beyond the schema, so baseline 3 is appropriate.

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 identifies the resource: MISO real-time transmission binding constraints, including specific flowgates, facility limits, and shadow prices. The line 'A binding constraint is why LMPs diverge between nodes' and the example queries distinguish it from sibling MISO data tools like miso_lmp.

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 explicitly says 'Use for' and lists concrete queries such as 'why is MISO congested' and 'which flowgate is driving the price spread.' It does not name sibling alternatives or state when not to use it, but the context is clear enough for an agent to select it correctly.

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