create_reference_list

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

With no annotations, the description carries full burden but provides no behavioral details: no mention of side effects, permissions, whether it overwrites existing lists, or what response to expect. Calling it a 'mutation' only implies a write, which is insufficient.

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 extremely short but under-specifies, not truly concise. It includes a variable list and an example that is cut off, providing no coherent structure or useful content. Every sentence should serve a purpose, and this does not.

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 7 parameters, no output schema, and no annotations, yet the description gives no overview of the operation's purpose, expected behavior, or result. Given the complexity of creating a reference list (with columnSelector, filter, order, input), the description is severely incomplete.

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 description lists variable names but does not explain their purpose or format beyond what the schema already provides. The example variables give some hint but are truncated and not explained. The schema descriptions ('GraphQL: String') are minimal, so the description fails to add meaningful semantic 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 only repeats the mutation name 'createReferenceList' with no verb phrase or explanation of what a reference list is or what creation entails. It does not clearly state the tool's function, making it a near-tautology.

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 the many sibling tools for reference lists (update_reference_list, delete_reference_list, create_reference_list_row, etc.). There is no mention of prerequisites or intended use cases.

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