fossa_set_package_label_assignments

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

Beyond the annotations, the description discloses key behavioral traits: it is destructive (removes unmentioned assignments), requires both FOSSA_ALLOW_WRITES and FOSSA_ALLOW_DESTRUCTIVE, and warns about clobbering others' labels. It also explains the reconcile semantics and empty-list clearing behavior, which the annotations alone do not convey.

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 concise and logically ordered: purpose, warnings, reconcile semantics, prerequisite read, parameter clarification, and alternative tool. Every sentence adds value and none are redundant.

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?

For a destructive write tool with nested object parameters and no schema descriptions, the description covers purpose, usage, destructive implications, prerequisites, parameter semantics, and alternatives. The output schema exists, so return details need not be described. It is fully sufficient for correct invocation.

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 well for the most complex parameter `new_label_ids`, clearly defining its key-value mapping, the literal 'all' for all versions, and empty-array clearing. It does not explicitly explain `scope_id`, but the schema's enum and default null provide some structure.

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-resource pair: 'Replace a package's label assignments at one scope with an exact desired state.' It clearly distinguishes this from related tools by labeling it a 'reconcile, not an addition' and by contrast with fossa_assign_package_labels.

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?

Explicitly states when to use this tool versus the alternative, recommending fossa_assign_package_labels for additive intent. It also instructs to read current state with fossa_list_package_label_assignments first, and highlights required environment variables for writes/destructive operations.

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