List partitions

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful output context (availability, MIG vs full H100, preempt notes), but says nothing about authentication/profile resolution behavior despite the open-world hint.

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?

A single front-loaded sentence with no wasted framing. The parenthetical is terse to the point of being hard to parse, but the size is appropriate for a list tool.

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 read-only tool with no output schema, the description does sketch the return contents (availability, MIG vs full H100, preempt notes), which is the right instinct. However, the undocumented 'partition' enum leaves a real gap in how to invoke it correctly.

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 only 50%: 'profile' is documented in the schema, but the 'partition' enum carries no description of what each value means (general-short, general-bigmem, etc.). The description does not compensate at all, so an agent cannot infer what filtering by a given enum value returns.

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 ('Show') and resource ('RIS Compute2 partitions') and adds that the output includes availability and plain-English notes. An agent can tell it is a listing tool, though it does not explicitly contrast itself with siblings like ris_list_modules or ris_list_conda_envs.

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?

No guidance on when to call this versus other list/discovery tools, and no explanation of when to supply the 'partition' argument versus omitting it. The 'no plain general' aside hints at scope but is cryptic rather than instructive.

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