create_reference_list_row

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely labels the operation as a 'mutation' without explaining side effects, required permissions, return behavior, or error conditions. The example variables hint at structure but not 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?

The description is very short and front-loaded with the mutation name, but it lacks a proper explanatory sentence. The example is useful but the overall structure feels like a stub rather than a well-crafted description. It is concise yet under-specified.

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?

For a mutation tool with no annotations, no output schema, and only two parameters, this description is severely incomplete. It does not explain what the tool accomplishes, what the return value is, or any operational details. Users would need external documentation to use it correctly.

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 input schema only says 'GraphQL: CreateReferenceListRowInput!', which is unhelpful. The description compensates by providing an example variable structure ('referenceList' and 'values' with 'column' and 'value'), adding meaningful semantics beyond the schema. However, it does not explain each field's purpose.

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 restates the tool name as 'mutation createReferenceListRow' and gives a variable template, without explicitly stating that it creates a new row in a reference list. It lacks a clear verb+resource statement and does not distinguish it from sibling tools like update_reference_list_row or delete_reference_list_row.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools exist for related operations (update, delete, create reference list), but the description provides no context about appropriate use cases, prerequisites, or scenarios where this tool is preferred.

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