fossa_manage_team_group

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

The description goes well beyond the annotations by disclosing that FOSSA's update endpoint replaces both editable fields rather than patching, that deletion removes team associations and membership lists but not the teams themselves, and that there is no undo. It also explicitly warns about the destructive nature of delete, complementing the destructiveHint and idempotentHint annotations with concrete consequences.

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 efficiently organized: a one-line summary, a clear warning about writes and permission flags, then action-specific parameter requirements, and finally deletion behavior. Every sentence adds necessary information, and the structure front-loads the most critical facts (purpose, write safety, permissions) before diving into details.

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 (three actions, three permission flags, destructive side effects, field replacement semantics), the description covers all essential aspects: what the tool does, how each action maps to parameters, what deletion affects, and which sibling tool handles the related but distinct task of changing team assignments. The presence of an output schema means return-value documentation is not required, so the description is fully sufficient.

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?

With 0% schema description coverage, the description compensates by explaining the role of each parameter in the context of each action. It clarifies that name and default_role_id are the two editable fields and that team_group_id is required for update/delete. However, it does not elaborate on the meaning of default_role_id beyond its schema title, so it stops short of full semantic coverage.

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 'Create, rename, or delete a FOSSA team group,' a specific verb+resource statement that exactly matches the tool name and clearly differentiates from sibling tools. It further distinguishes itself by noting it covers three actions rather than three near-identical tools, and explicitly names fossa_update_team_group_assignments as the alternative for changing team membership.

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 explicit per-action requirements (create needs name+default_role_id, update needs team_group_id plus both, delete needs only team_group_id) and states when to use this tool vs. the related assignment tool. It also specifies environmental prerequisites (FOSSA_ALLOW_WRITES, FOSSA_ALLOW_ADMIN, FOSSA_ALLOW_DESTRUCTIVE for delete), giving clear when/when-not guidance.

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