sas_connection_save

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

Annotations already declare the non-read-only, non-destructive profile. The description usefully adds upsert semantics ("create or update") and the activate side effect, which go beyond the annotations, but says nothing about permissions required, behavior on update of existing settings, or what fields are overwritten.

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 carrying the verb, resource, and field inventory. The long parenthetical field list is dense but each item earns its place; no filler sentences.

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 mutation tool with no output schema and nested-object input, the definition covers the connection fields but leaves the two scalar parameters undocumented and gives no return or post-save behavior. Annotations carry the safety profile, but the update/rename semantics remain underspecified.

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 0%, so the description must compensate. It enumerates fields inside the nested ``connection`` object (name, Viya address, compute context, client ID, etc.), which adds real meaning, but it never explains the ``activate`` or ``original_name`` parameters — critically, ``original_name`` is undocumented despite being needed for the rename/update path.

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 specific upsert operation ("Create or update a saved SAS Viya connection") and enumerates the relevant connection fields, so an agent knows the resource and scope. It partially differentiates from close siblings like sas_connection_activate and connection_save by noting the activation side effect, but does not clearly distinguish this tool from the near-identical connection_save sibling.

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?

Usage is implied rather than stated: the parenthetical field list and the note about ``activate`` hint at when saving applies, but there is no explicit when-to-use guidance or exclusion versus sas_connection_activate/sas_viya_save/connection_save. The agent must infer the conditions.

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