skypilot_realtime_slurm_gpu_availability

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds 'real-time' and the output content (GPUs and quantities), which are useful behavioral details, but it omits rate limits, auth, or data freshness guarantees.

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?

Three short sentences, front-loaded with the core purpose. No wasted words; each sentence adds a distinct piece of information.

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?

The description covers purpose, output summary, and all filters. With an output schema present and annotations covering read-only safety, it is largely complete, though it could clarify how multiple filters combine or the format of the cluster name.

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 the description must compensate. It maps each of the three filters to its purpose (GPU name, minimum quantity, Slurm cluster name), adding meaningful semantics beyond the bare parameter names, though it does not specify matching syntax or defaults.

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?

States a specific verb ('Get real-time GPU availability') and resource ('Slurm cluster'), and the scope 'Slurm' distinguishes it from the sibling realtime_gpu_availability tool. An agent can identify its purpose without opening the schema.

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?

Provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as skypilot_realtime_gpu_availability or list_accelerators, nor prerequisites like authentication.

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