list_columns

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'List' implies a read-only operation with no side effects, which is minimal but acceptable. However, it does not explicitly state read-only nature, permissions, or return behavior, so it only partially reveals behavioral traits.

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 a single, concise sentence with no filler words. It directly states the tool's purpose and is appropriately sized for the simple operation.

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 tool has no output schema or annotations, and the description is sparse. It does not specify what information the response contains (e.g., column names, metadata), nor does it mention how listId relates to other tools like list_lists. The description is minimally adequate for a trivial read operation but lacks important contextual details.

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 coverage is 0%, so the description must compensate for the undocumented parameter. It mentions 'a SharePoint list' but does not explicitly explain that the 'listId' parameter is the list identifier, how to obtain it, or its format. The parameter name is self-explanatory, but the description adds little beyond the 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?

The description uses a specific verb ('List') and a clear resource ('columns in a SharePoint list'), which unambiguously identifies the tool's function. It differentiates from sibling tools like list_lists (lists vs. columns) and list_items (items vs. 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 gives no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. It only states the basic function, so the usage context is entirely implied.

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