sas_viya_sign_in

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

Annotations already declare the tool is not read-only and not destructive. The description adds important behavioral context: it opens a browser and defines a two-step flow. It still omits auth details, token handling, and error behavior.

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 compact sentences, front-loaded with the two cases, with no wasted words.

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?

Covers the core two-step flow for a simple sign-in tool with no output schema. Missing sibling context and any mention of prerequisites or failure modes, but complete enough for correct 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?

Schema has no parameter description (0% coverage), so the description must compensate. It explains that `code` is the value shown by SAS Logon and that its absence triggers a browser-open flow, adding meaning beyond the bare schema.

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 action (sign in to SAS Viya) and clearly distinguishes two modes based on the presence of `code`. Does not differentiate from siblings like `sas_viya_sign_out` or `connection_sso_sign_in`.

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?

Explains when to call without `code` (open browser) and with `code` (finish sign-in), giving clear context for each mode. Does not mention alternative tools or exclusions.

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