set_cluster_rate

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

Without annotations, the description carries full burden. It discloses 'Write operation — recorded in the audit log', indicating it is auditable. It does not detail side effects or validation limits, but the write nature is clear.

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 concise with no wasted words. It front-loads the core purpose, then provides brief context and structured parameter details. Every sentence serves a purpose.

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 three parameters, no output schema, and no annotations, the description covers purpose, usage conditions, audit logging, and parameter meanings. It lacks error conditions or return value details, but is otherwise complete.

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%, so description must compensate. It provides an Args section with clear explanations: cluster_name as 'Name of the cluster', rate_per_gpu_hour with an example '$2.50/GPU/hr', and currency with default 'USD'. This adds meaningful context beyond schema titles.

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 clear verb-resource pair 'Set the GPU cost rate for a cluster.' It explicitly states the purpose and distinguishes from siblings like get_cluster_rate and get_cost_estimate by explaining it is required to enable cost estimates.

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 provides usage context: required to enable cost estimates, can be updated at any time, and requires organisation admin role. It lacks explicit when-not-to-use but gives clear prerequisites.

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