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

Annotations already declare the safe read-only/idempotent profile, and the description goes further with substantive behavioral context: an API key requirement, pricing tiers, refund terms, and a redistribution-terms caveat. This is genuinely useful auth and licensing disclosure beyond the structured fields.

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?

Front-loads the data scope in the first sentence, then appends auth/pricing constraints. Three sentences with little waste, though the pricing/refund detail is somewhat promotional relative to tool-selection value.

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?

An output schema exists so return values need not be explained, and the description covers data content plus auth constraints. The main gap is the unexplained 'params' object, but overall the definition is adequate for an internal query tool.

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 0% and the single parameter is an untyped free-form 'params' object. The description lists data facets (unit counts, storage variants, suppression atoms) but never explains what the params object should contain or how to structure it, leaving invocation semantics opaque.

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?

States a specific verb ('Query') and a precise resource ('MISO Schedule 53 class-average and indicative-DLOL seasonal accreditation ratios'), with additional detail on unit counts, storage variants, and suppression atoms. The MISO scope distinguishes it from the PJM counterpart, though it never explicitly names the sibling to route against.

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?

Implies usage for MISO accreditation data and adds a real usage constraint ('not included in the 25 free queries'), but gives no explicit when-to-use vs the PJM sibling or other capacity tools, and no when-not guidance.

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