access_group

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 only says 'query accessGroup' and lists variables, not mentioning the response shape, pagination behavior, permissions, or nested resources. This is insufficient for a 14-parameter GraphQL query.

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 not well-structured. It is a fragment followed by a variable list and a truncated example. While it avoids verbosity, it under-specifies the tool's purpose and usage, making it more under-specified than concise.

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 tool with 14 parameters, no output schema, and no annotations, this description is completely inadequate. It does not explain what the query does, how parameters interrelate, or what the response contains. The example variables hint at some structure but are incomplete and cut off.

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?

Schema descriptions are minimal ('GraphQL: String', etc.), but coverage is 100%. The description adds a truncated example variables object showing filter structure ('accessGroups', 'customers', 'ids', 'name', 'roles', 'users'), which provides some semantics beyond the schema. However, most parameters (after, first, order, etc.) remain unexplained.

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 reads 'Access Groups · query accessGroup', which essentially restates the tool name as a GraphQL field. It fails to specify that this tool retrieves a single access group by ID or explain what it returns. No differentiation from sibling tools like access_groups.

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 such as access_groups (list) or create/update/delete tools. The required 'id' parameter implicitly suggests fetching a specific access group, but this is never stated explicitly.

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