execute_sas_code

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

With no annotations, the description explains the multi-step behavior (create definition, execute, retrieve results), which goes beyond the schema's simple parameter description. It does not disclose potential side effects, permissions, or the exact nature of returned results, but the core behavior is transparent.

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?

Two sentences: the first front-loads purpose, the second adds process detail. There is no redundancy or wasted wording, making it highly concise and well-structured.

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 and process but leaves the exact return value ambiguous—'information about the completed Job' versus 'retrieve the results' could mean metadata, logs, or actual output data. Without an output schema, this gap prevents full completeness, though the tool's scope is simple.

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 sole parameter sas_code is already well described in the schema as 'the SAS code snippet to be executed using the Viya Job Execution API Service', so the description adds no extra parameter-level meaning. With 100% schema coverage, the baseline of 3 is appropriate.

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 clear verb 'Executes' with a specific resource 'SAS code in the Viya environment' and an outcome 'returns information about the completed Job'. It distinguishes itself from sibling job-management tools by focusing on ad-hoc code execution rather than batch submission or status queries.

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 description implies the tool is for running supplied SAS code and clarifies it does so by creating a job definition, executing, and retrieving results. It does not explicitly contrast with siblings like submit_batch_job or list_jobs, nor give when-not-to-use guidance, but the intended context is clear.

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