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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description isn't burdened with safety disclosure. It adds value by documenting the return structure ('List of nodes with keys: name, import, alias_of (optional)') and giving concrete examples for both parameters. This is richer than the TDQS 3 baseline for annotated tools, though it stops short of covering edge cases or error behavior.

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 compact and well-structured: a one-sentence purpose statement, an Args list, and a Returns list. Every sentence conveys necessary information with no filler or repetition of the schema. The front-loaded main clause immediately tells the agent what the tool does.

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?

Given the tool's simplicity (2 required params, no enums, no nested objects), the description covers all essentials: what it lists, how to specify provider/service, and what the return looks like. The sibling context is addressed through the explicit 'node classes' scope. There's no missing information that would leave an agent guessing.

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%, yet the description fully compensates by explaining each parameter with type, examples, and meaning: 'provider: Provider name (e.g. 'aws', 'gcp', 'k8s')' and 'service: Service category (e.g. 'compute', 'database', 'network')'. This transforms what would be bare strings into actionable guidance, exceeding the baseline required for low coverage.

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 starts with a specific verb+resource+scope: 'List available node classes for a provider.service combo.' This clearly distinguishes it from sibling tools like list_providers, list_services, and list_categories, which focus on other entity types. The phrase 'node classes' also clarifies the output granularity.

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 implies when to use this tool by specifying the 'provider.service combo' scope and listing examples, but it does not explicitly name alternative tools or state when not to use it. That said, the context is clear enough that an agent can infer usage, so it earns a 4 rather than a 3.

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