Create or update a team

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

No annotations are provided, so the description carries the burden. It discloses that the operation uses POST/PUT and that omitting teamId creates, while passing it updates. However, it does not explain effects on existing users (replace vs merge), required permissions, idempotency, or error handling. The HTTP semantics are helpful but incomplete for a mutation tool.

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 long, front-loaded with the action (Create/Update), and contains no filler. Every clause adds value: HTTP methods, body, and a usage example. It is concise yet informative.

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 has no annotations or output schema, and the description covers core usage (create/update, body, usage scenario). However, it omits the 'organization' parameter entirely and does not address update semantics (e.g., whether users are replaced or appended). The description is sufficient for basic use but incomplete for edge cases and full context.

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 covers the team object and teamId, but the description adds crucial meaning: how to select create vs update (omit or pass teamId). It also clarifies the team object structure (name, description?, users?). The 'organization' parameter remains undocumented in the description, but the overall parameter semantics are well explained 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 clearly states the tool's function: create a team via POST (omit id) or update via PUT (pass teamId). It explicitly distinguishes the two modes and provides the body structure. The verb 'Create/update' and resource 'team' are specific, and the HTTP method clarification removes ambiguity.

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 gives a concrete use case: "This is how you 'create a new team X and add these users to it'." This implies when to use the tool (team creation/update) and differentiates from siblings like list or delete. However, it does not explicitly state exclusions or alternatives, but the context clearly separates it from wflow_list_teams and wflow_delete_team.

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