delete_reference_list

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

Annotations are absent, and the description provides no behavioral details such as whether deletion is destructive, irreversible, or requires specific permissions. It merely names the mutation and its input variables.

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 verbose dump of variable names and an example, lacking a clear front-loaded purpose. It is cluttered and not concise despite being a single block.

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?

With no output schema and no behavioral context, the description is incomplete for a mutation that appears to delete a reference list. It does not mention return values, side effects, or how the listed variables interact, making it inadequate for a tool with seven parameters.

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 covers all parameters with basic GraphQL type descriptions, the tool description's example variable JSON demonstrates the expected structure, offering some practical guidance. However, semantic meaning (e.g., that 'id' is the list to delete, or why pagination fields are present) is not explained.

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 deleteReferenceList' essentially reiterates the tool's name without explicitly stating that it deletes a reference list. It fails to define the operation's effect, making it a 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 alternatives like delete_reference_list_row or update_reference_list. The description only lists variables and an example payload, offering no contextual direction.

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