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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the scope caveat that the fiber layer covers only California's state middle-mile network and not nationwide fiber, which prevents a serious misinterpretation of results.

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?

Four short sentences, front-loaded with the returned fields and then the default-vs-parameter behavior; nothing is padding. The line-wrapped fragments are slightly choppy, but each sentence earns its place, including the fiber-coverage caveat.

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?

With an output schema present, the description need not document return shapes, and its job narrows to scope, default behavior, and caveats – all of which it covers. For a one-parameter, read-only catalog tool this is close to complete; only the dataset-key format is left unspecified.

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 0% – the single 'dataset' property has no description at all – so the description carries the burden, and it does: the default/null behavior (overview of all datasets and layer keys) and the non-null behavior (product metadata, operators, energy regions) are both spelled out. It does not give the key format or examples (e.g. 'fiber'), which leaves some ambiguity against the 160-char string constraint.

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?

Opens with a specific verb+resource ('List Korzy's datasets') and immediately enumerates the content of each entry: geographic coverage, source dates, grid interfaces, and query limits. That enumeration makes it unmistakable that this is the catalog/enumeration tool rather than one of the sibling 'get_<asset>' lookups.

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?

It clearly splits the two usage modes: no argument returns an overview retaining every dataset and layer key, while passing a dataset key returns product metadata such as operators or energy regions. It stops short of naming alternative tools or stating any exclusion conditions, so it is clear-context guidance rather than full routing guidance.

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