list_compute_columns

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

No annotations are provided, so the description must carry all behavioral disclosure. It states the tool runs in a compute session, but it does not disclose whether it is read-only, what permissions are required, or any side effects. For a tool that retrieves metadata, this is minimal.

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 two short sentences, each adding value. It is front-loaded and concise with no redundant or missing information.

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?

Given the parameter count (6) and the presence of an output schema, the description is adequate but lacking. It does not explain pagination (limit, start), filter behavior, or the relationship to the compute session beyond a brief mention. The output schema likely covers the return format, so the description is minimally complete.

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?

All 6 parameters are described in the input schema with 100% coverage. The description adds no additional parameter-specific information beyond what the schema provides. Baseline 3 is appropriate as the schema carries the burden.

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 lists columns of a table in a SAS library within a compute context. It specifies the resource (columns of a table), the action (list), and the context (compute session). It distinguishes from sibling tools like list_compute_tables, which lists tables, not columns.

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 mentions it runs in a reusable per-user session, implying a specific usage scenario, but it does not provide explicit when-to-use vs when-not-to-use guidance or mention alternatives like get_castable_columns. The usage is implied but not fully clarified.

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