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

No annotations are supplied, so the description carries the full disclosure burden. It does indicate the tool returns reference guidance and cost ranges (read-only, informational, zero-param), but says nothing about the form of the response, whether the figures are static or regional, or any caveats on cost estimates.

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?

A single front-loaded sentence with zero filler, covering both sizing rules and cost ranges. It is a sentence fragment rather than a statement of what the tool does, which slightly weakens clarity but costs no extra length.

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 zero-parameter reference tool with no annotations and no output schema, the description conveys the topic adequately and an agent could call it without risk. It stops short of saying what the answer looks like or how the sizing rules and cost ranges relate, leaving a modest gap.

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?

The input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is missing.

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 names a specific resource: generator sizing rules of thumb plus typical installed cost ranges, scoped to standby generators. It is a noun phrase with no verb and does not distinguish itself from siblings such as compare_generators or catalog_info, but the content an agent would retrieve is unambiguous.

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?

There is no guidance on when to call this versus search_generators, compare_generators, or catalog_info. An agent must infer that this is the pre-selection sizing/cost reference rather than a lookup of actual products, and nothing states whether it should be consulted before or after searching.

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