create_reference_list_column

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects, required permissions, irreversibility, or any outcomes beyond the example input. This is a significant gap for a mutation tool.

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 very short and lacks structure. It is essentially a code snippet without a plain-language explanation. This is under-specification rather than concise, as it does not efficiently convey key information that an agent needs.

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 is a mutation with no output schema and no annotations, yet the description does not cover return values, errors, prerequisites, or any operational context. It is completely inadequate for a tool of this complexity.

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?

While the schema's 'input' description is generic ('GraphQL: CreateReferenceListColumnInput!'), the description provides an example variable structure with fields like name, referenceList, and type, which adds some meaning. However, the example uses empty strings and does not fully explain each field's purpose. With schema coverage at 100%, a baseline of 3 is appropriate given the minimal added value.

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 'Reference Lists · mutation createReferenceListColumn' essentially restates the tool name and provides a GraphQL mutation reference. It gives no plain-language explanation of what the tool does, though the example variables hint at creating a column in a reference list. This is a tautology of the name with minimal added context.

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?

No guidance is provided on when to use this tool versus alternatives like create_reference_list_row or update_reference_list_column. The description contains only a technical reference and example variables, with no context for use.

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