fossa_list_oidc_provider_service_accounts

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

The description reinforces the readOnlyHint annotation with 'Read-only.' and adds valuable context: 'Returns account ids, usernames, and email addresses — identity, not credentials.' This clarifies the nature of returned data and sets expectations about sensitive information. It also explains the team_id behavior, going beyond the annotation's simple read-only flag.

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 organized into three short paragraphs: purpose, usage guidance, and return semantics. It is front-loaded with the main action, and every sentence adds meaningful information without redundancy. There is no filler or unnecessary detail.

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 presence of an output schema and readOnly/openWorld annotations, the description covers the essential operational context: what the tool does, when to use it, a key parameter nuance, and what kind of data is returned. It does not explicitly discuss pagination, but the parameter names (`page_size`, `prev`) make that inferable, so the omission is minor.

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?

The schema has 0% description coverage, so the description must compensate. It explains the role of `team_id` (required for team-level tokens) and implies `provider_id` through the OIDC provider context. However, pagination parameters `prev` and `page_size` are left undocumented, so the description only partially 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 first sentence states 'List the service accounts that may be named in a new trust relationship for an OIDC provider.' This uses a specific verb (list) and resource (service accounts) with a clear scope ('may be named in a new trust relationship'). It distinguishes the tool from sibling OIDC tools like list_oidc_providers or list_oidc_trust_relationships by focusing on service accounts available for trust relationships.

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 explicitly states 'Use this before fossa_create_oidc_trust_relationship to find the user_id to grant.' This gives a precise when-to-use instruction and names the companion tool. It also notes the `team_id` requirement under team-level permissions, providing concrete context for when that parameter matters.

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