sas_session_reset

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description must add the behavior — and it does: it explains that the current sessions are terminated and the next run provisions new ones with startup code executed again. It does not mention that in-memory/work state in those sessions is lost, which is the one remaining gap.

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 the action first and the consequence second. No filler, nothing that can be cut.

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?

With no parameters, no output schema, and a simple lifecycle action, the description covers what an agent needs to call it correctly and anticipate the side effect. The only missing piece is an explicit warning that current session state (work tables, librefs) is discarded rather than carried over.

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 tool takes zero parameters, so the baseline is 4. There is nothing parameter-related for the description to clarify.

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 ("End") and resource ("SAS Compute and CAS sessions") plus the resulting scope of the operation. An agent can distinguish this from siblings such as sas_viya_sign_out or restart_server without opening any 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?

The implied use case (you want fresh sessions so startup code re-runs, e.g. after config changes) is conveyed by the parenthetical, but there is no explicit when-to-use/when-not-to guidance and no naming of alternatives like restart_server or sas_viya_sign_out.

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