Get Coolify Project

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

Discloses that it returns 'full details' including environments and resources, adding context beyond readOnlyHint and idempotentHint annotations. No contradictions; safety profile is consistent.

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?

Single sentence, no unnecessary words. Front-loads the action and result. Every part earns its place.

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?

Adequate for a simple retrieval tool with 3 parameters and no output schema. Mentions the key data returned (environments and resources). Could be improved by noting the response format but not strictly necessary given the tool's simplicity.

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 coverage is 100%, so baseline is 3. The description adds the context about 'including its environments and resources' which slightly enriches the understanding of the uuid parameter but does not add semantic details for reveal or instance beyond their 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?

Clearly states the verb 'Get', resource 'project', and retrieval criteria 'by UUID'. Distinguishes from sibling tools like list_projects and update_project by specifying it returns full details for a single project including nested environments and resources.

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 implies when to use (for a single project detail), but does not explicitly state when not to use or mention alternative tools. No guidance on prerequisites like needing the UUID.

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