get_infra_billing_nodes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the '[READ]' tag simply restates that. The description adds no pagination behavior, response shape, scoping, or auth context beyond the bare endpoint path.

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?

Extremely terse and front-loaded with no wasted sentences. It is not under-specified to the point of being a single word, but the brevity is achieved by omitting content rather than by tight editing.

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 no output schema and no parameters, the description carries the whole burden of explaining what this read returns, and it says nothing. Among 80+ get_* siblings, an agent cannot tell what a 'billing node' is or when this result is useful.

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 the schema is trivially complete at 100% coverage and there is nothing for the description to explain. Baseline 4 applies for a no-parameter tool.

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 states a verb and resource ('Get infra billing nodes') and includes the HTTP endpoint, so the basic operation is identifiable. However, 'infra billing nodes' is never disambiguated against siblings like get_infra_billing_records, get_nodes, or get_infra_providers, leaving the agent to guess what this resource actually contains.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the ~80 sibling tools. The agent gets no signal for choosing this over get_nodes or get_infra_billing_records.

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