fossa_update_team_assignments

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

Beyond the annotations (destructiveHint, openWorldHint), the description adds crucial behavioral details: exactly which actions require FOSSA_ALLOW_DESTRUCTIVE, how 'replace' clears unbounded sets, that all_projects/project_filters are resolved server-side and may affect an unknown number of projects, and the prerequisite that projects in a release group must already be on the team. This is rich, non-redundant 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?

While the description is long, it is tightly structured with bullets and bold warnings. Every sentence adds essential information—permissions, target-specific argument rules, action behavior, and destructive edge cases. The front-loaded purpose and requirements make it easy to scan, and there is no redundant fluff.

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?

Given the tool's complexity (8 parameters, 3 targets, 3 actions), the description is remarkably complete. It covers all parameter combinations, special cases like unbounded project sets, validation behavior, prerequisites for release groups, and permission gates. The presence of an output schema means return values don't need description, and the behavioral and semantic coverage is thorough.

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 input schema has 0% description coverage, so the description carries full responsibility for parameter meaning—and it delivers. For each target, it explains which parameters apply and their structures (e.g., users require id and roleId for add/replace; project_filters accepts title, labels, type, etc.). It also clarifies action semantics (replace sets exactly what is named) and that mismatched arguments are rejected.

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 opens with a specific verb and resource: 'Change what is assigned to a FOSSA team' and enumerates the three assignment types (members, projects, release groups). This clearly distinguishes the tool from sibling tools like fossa_update_team (team metadata) and fossa_manage_team_group.

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 clear context on when to use the tool (for any of three assignment targets) and details how each target uses different arguments. It states required environment variables (FOSSA_ALLOW_WRITES, FOSSA_ALLOW_ADMIN, etc.) and when destructive permission is needed. However, it doesn't explicitly mention when not to use this tool or name alternatives, so it falls short of a 5.

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