list_compute_contexts

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

The description states 'list', implying a read-only operation, but does not explicitly confirm no side effects, no authentication details, or any constraints. With no annotations, the description carries the full burden and provides only minimal transparency.

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 a single concise sentence. However, it is overly minimal given the tool's complexity and sibling context. While front-loaded, it could include more value without sacrificing conciseness.

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?

Despite having an output schema (not provided), the description fails to contextualize parameters or usage. With no annotations and a large sibling list, the description is incomplete for effective tool selection and invocation.

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 input schema has three parameters with defaults (limit, start, filter_name), but the description provides zero explanation. With 0% schema description coverage, the description should compensate but fails to clarify pagination (limit, start) or filtering (filter_name).

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 clearly states the tool's purpose: listing available compute contexts on the Viya environment. It is specific, uses a clear verb-resource structure, and is distinguishable from sibling tools like list_caslibs or list_jobs.

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 use this tool versus alternatives. For example, does it provide contexts needed for creating ML projects or running jobs? The description lacks context for selecting this tool over others.

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