create_access_group

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

With no annotations available, the description carries full responsibility for disclosing behavioral traits. It labels the operation as a 'mutation' but does not state that it creates a new access group, what permissions are required, whether it is reversible, or what side effects occur. The parameter list adds no behavioral context.

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 raw dump of GraphQL variable names and a long example JSON, without a clear, front-loaded purpose statement. It is not well-structured for quick comprehension and redundantly lists parameter names that are already present in the schema.

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 with 14 parameters, no annotations, and no output schema, the description is severely inadequate. It fails to explain the tool's function, appropriate usage, or behavioral consequences. The auto-generated GraphQL information does not provide the necessary context for an agent to correctly select and invoke this tool.

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?

All 14 parameters have schema descriptions (100% coverage), so the baseline is 3. The description does list the parameter names and an example variables object, but these names are already in the schema and the example is truncated and unexplained, adding minimal semantic value 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 is essentially a restatement of the tool name: 'Access Groups · mutation createAccessGroup.' It does not explain in plain language that this tool creates an access group. The phrase 'mutation createAccessGroup' is a tautology of the name 'create_access_group' and provides no additional clarity about the tool's function.

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 provides no guidance on when to use this tool versus alternatives like update_access_group or delete_access_group. It only lists parameters and example variables, with no mention of the appropriate context or scenarios where this mutation should be invoked.

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