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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds one domain rule — that fabric declarations do not confer EMT qualification — which is genuine extra context, but it is too terse to be actionable and omits freshness, scope, or result shape.

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?

It is short and front-loads the primary fact about the resource. The second clause is dense, undefined terminology placed as a semicolon fragment, which costs more confusion than the brevity saves.

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, read-only listing tool with no output schema, the description only needs to identify the resource and its scope, which it does. The missing piece is what the offer records contain and how current they are, but the annotation set covers the operational profile.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a no-parameter schema applies, with the only deduction being the absence of any hint about what a call yields.

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 the resource ("whole-node cluster offers") and implies a listing verb via "Current", so the object is identifiable. However, no explicit verb is given and the second clause ("fabric declarations do not establish independent EMT qualification") is unexplained jargon, so it does little to separate this from siblings like emt_cluster_quote or emt_rent_cluster.

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 statement of when to call this versus emt_cluster_quote, emt_rent_cluster, or emt_cluster_quote's siblings, and no prerequisites are mentioned. The qualification caveat hints at a boundary condition but never says what to use instead when that condition applies.

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