fossa_list_addable_team_targets

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

The description adds behavior beyond the readOnlyHint: it discloses the type discriminator on entries, the no-paging exception, and the constraint that all projects of a release group must be on the team first. This is useful, non-obvious context that annotations do not provide.

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 three sentences: a clear lead, a 'Read-only' note, and a structured breakdown of the three targets. Every sentence communicates necessary information without redundancy or 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?

An output schema exists, so return values are already covered. The description explains the domain-specific nuances (release group prerequisite, target distinctions, pagination differences) making the tool fully usable. A slight gap is not framing this relative to team update workflows, but that is not essential.

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 carries the burden. It fully explains the target enum values and when release_group_id is required. It does not explain team_id, page, or search, but those are self-explanatory and have schema defaults, so the description sufficiently compensates for the most critical parameter.

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 starts with 'List what could still be added to a FOSSA team' — a specific verb+resource+scope. It then enumerates the three target types, making it unmistakable what the tool returns and distinguishing it from siblings like fossa_get_team or fossa_update_team_assignments.

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?

It clearly explains when to use each target: users for org members not yet on the team, projects_and_release_groups for all assignable items, and release_group_projects for a specific release group's missing projects. It also notes the no-paging behavior for the latter, which helps an agent choose based on data volume. It does not explicitly name alternative tools, but the guidance is otherwise strong.

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