fossa_enable_security_policy

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

Annotations already indicate write semantics (readOnlyHint=false), but the description adds valuable context: it explicitly says 'WRITES TO FOSSA,' requires FOSSA_ALLOW_WRITES=true, and explains the exact side effect—setting all three components (policy, scanning, status check). This goes beyond annotations by detailing operational prerequisites and the conceptual mechanism.

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 moderately concise with three paragraphs. The first sentence gets straight to the point, the second warns about write requirements, and the third explains the concept and parameter. Every sentence adds value, though the conceptual paragraph could be tightened. Overall well-structured and front-loaded.

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 (write operation, multiple settings, prerequisite), the description covers key aspects: the three components, the write requirement, and a critical parameter caveat. It lacks explicit detail on project_locator format and does not describe failure modes, but the presence of an output schema and annotations fill some gaps. It is sufficiently complete for an agent to invoke it correctly.

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?

Schema description coverage is 0%, and the description provides crucial semantics only for security_policy_id (numeric id from URL, no API to list). It indirectly clarifies enable_scanning and enable_status_check via the 'three components' explanation, but project_locator receives no elaboration. While helpful for one critical parameter, the description does not fully compensate for the lack of schema descriptions across all parameters.

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 states a specific verb-resource pair: 'Assign a FOSSA security policy to a project and turn on the enforcement that blocks packages violating it.' It clearly distinguishes from siblings like fossa_assign_security_policy_to_projects by explicitly noting this tool also enables scanning and status check, not just assignment.

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 clear prerequisite: 'Requires FOSSA_ALLOW_WRITES=true.' It also explains that blocking is the combination of three settings and that this tool 'sets all three,' implying when to use it versus alternatives that only handle one component. However, it does not name explicit alternatives or state when not to use it.

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