fossa_create_oidc_trust_relationship

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

Goes far beyond the annotations by disclosing the permanent, credential-less security implications, the exact environment requirements, wildcard matching behavior, and the risk of enabling admin tier without caller authentication. The description adds substantial behavioral context that annotations alone 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 detailed but every sentence contributes essential value, from the high-level summary to security warnings to parameter semantics. The most important warning is front-loaded and the structure flows logically from 'what it does' to 'why it is dangerous' to 'how to use it safely'.

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 high-risk, mutating, security-sensitive tool with no schema descriptions and a low-ambiguity name, the description is remarkably complete. It covers prerequisites, security caveats, parameter details, scoping, and data sourcing. The output schema exists, so the absence of return-value explanation is not a gap.

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?

Despite 0% schema coverage, the description thoroughly explains required_claims (claim, value, hasWildcards, sub pinning, wildcard refusal), audiences, user_id lookup, and scope/scope_id semantics. It even provides an example for sub. This fully compensates for the missing schema descriptions.

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 uses a specific verb + resource ('Grant a workload permanent password-less login to FOSSA as a specific service account') and clearly states the outcome. It distinguishes itself from sibling tools like fossa_create_oidc_provider and fossa_exchange_oidc_token by focusing on trust relationship creation.

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?

Provides concrete guidance: requires FOSSA_ALLOW_WRITES=true and FOSSA_ALLOW_ADMIN=true, tells how to find user_id via fossa_list_oidc_provider_service_accounts, and explains how to use scope='team' with scope_id. However, it does not explicitly state when not to use this tool or name alternative tools for different scenarios.

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