create_pod

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

No annotations are provided, so the description carries the full burden. It only states 'mutation' (a trivial fact already implied by the name) and gives no details on side effects, required permissions, reversibility, or return behavior. The description is essentially empty of 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 bloated dump of variable names followed by a long, truncated JSON example. It is not front-loaded with the core purpose, and much of the content is irrelevant or confusing. It would be far more concise to simply say 'Creates a pod' and describe the input.

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 15-parameter mutation with no output schema, this description is grossly incomplete. It does not explain what a pod is, what fields the input requires, what the mutation returns, or any prerequisites. The misleading example further detracts from completeness, making the tool nearly impossible to use correctly based on the description alone.

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 schema descriptions are just GraphQL type names (e.g., 'GraphQL: String'), which provide no domain meaning. The description lists 15 variable names but does not explain their roles, and the required 'input' parameter is not described at all. The example variables are irrelevant to a create mutation, failing to compensate for the schema's deficiency.

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 says 'Access Groups · mutation createPod', which essentially restates the tool name without explaining what a pod is or what the mutation does. The 'Access Groups' prefix adds confusion rather than clarity, and there is no differentiation from sibling tools like create_access_group or update_pod.

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. The example variables shown correspond to a query (with pagination and filters), not a mutation, which is misleading and could lead the agent to use it incorrectly.

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