coolify_get_team_members

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

No annotations are provided, so the description carries full burden. It indicates a GET request (read-only) but does not disclose any other behavioral traits such as required permissions, rate limits, pagination, error responses, or side effects. The minimal statement is not misleading but lacks depth.

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 a single sentence of 15 words that immediately conveys the action, resource, and endpoint. No filler or redundancy. It is optimally concise for its purpose.

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 simple one-parameter read tool, the description is adequate but not fully complete. It does not mention the return format (e.g., list of member objects) or any filtering/pagination behavior. Since no output schema exists, a brief note on the expected result would improve completeness.

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 100% with team_id described as 'ID of the team'. The description adds value by explaining how the parameter is used in the API call ('by ID (GET /teams/{id}/members)'), which clarifies the URL mapping. This goes beyond the schema's bare description.

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 clearly states the action (List members), the resource (members of a specific team), and the required identifier (by ID). It also includes the HTTP endpoint for further clarity. This distinguishes it from sibling tools like coolify_get_current_team_members and coolify_list_teams.

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 does not provide any guidance on when to use this tool versus alternatives. It simply describes the action without mentioning when to choose this over coolify_get_current_team_members or coolify_list_teams. Implicit differentiation from tool names is insufficient.

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