coolify_get_current_team

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the HTTP method (GET) and path, which implies a read-only operation, but does not mention idempotency, side effects, error handling, or authentication requirements. It adds minimal value beyond the schema.

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, well-structured sentence that conveys the purpose and the underlying endpoint without any extraneous words. It is front-loaded and efficient.

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 no output schema and no parameters, the description explains the input context (team bound to token) but does not describe the return value (e.g., team object structure). For a simple tool, this is adequate but could be improved by mentioning the output format or error conditions.

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 input schema has zero parameters, so schema documentation coverage is 100% by default. The description adds meaningful context by specifying that the retrieved team is 'bound to the API token', which explains the implicit parameter (the token). This goes beyond what the schema provides.

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 verb 'Get' and specifies the resource as 'the team bound to the API token'. It also includes the REST endpoint (GET /team), which reinforces the action. This is distinct from sibling tools like coolify_list_teams (which lists all teams) or coolify_get_current_team_members (which gets members).

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 provides no guidance on when to use this tool versus alternatives such as coolify_list_teams or coolify_get_team_members. It does not explain that this tool is for retrieving the team associated with the current API token, nor does it mention any exclusions or prerequisites. The agent must infer usage from context.

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