Create Team

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

Annotations already declare readOnlyHint=false, so the mutating nature is known. The description adds domain context (teams used with auto-assign tickets) but does not disclose additional behavioral traits such as required permissions, duplicate handling, or side effects. With annotations present, the bar is lower, but no extra behavioral detail is added beyond the obvious create action.

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 two sentences and directly states the endpoint and purpose. The second sentence about auto-assign tickets is valuable context without unnecessary fluff. Every word earns its place.

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?

The tool is a straightforward create operation with a rich input schema that documents all parameters. The description provides the core purpose and domain context. It lacks explicit return-value information or authentication requirements, but for a simple create tool with well-documented params, it is largely complete.

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 description coverage is 100%, with each parameter (name, members, decoration, description) documented in the schema. The description does not add any additional meaning or syntax details for parameters, so the baseline of 3 applies.

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 'POST /api/teams — Create a new team' uses a specific verb and resource, clearly identifying the action. It is distinct from sibling tools like gorgias_list_teams, gorgias_update_team, and gorgias_delete_team, and adds useful context about the auto-assign tickets feature.

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 implies the tool is used for creating teams, and the note about auto-assign tickets gives context, but it does not explicitly state when to use this tool versus alternatives like updating or listing teams. No exclusions or 'when not to use' guidance is provided.

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