manifest

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

With only openWorldHint and no readOnly/destructive annotations, the description adds behavioral value by specifying the local file path, listing action signatures, and stating 'confirm for destructive ops' and 'optional instance'. It does not detail side effects of sync/prune or audit output, but it provides meaningful safety and scope context beyond the annotations.

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?

Two dense sentences: the first states purpose and resource, the second lists action signatures and safety information. The content is front-loaded and scannable, with no redundant words or filler.

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 multi-action CRUD/sync/diff tool with 12 parameters and a rich nested schema, the description provides the essential action-parameter matrix and safety caveat. Combined with the output schema, this covers most operational needs, though it does not explain the semantics of sync/diff/audit actions or clarify UUID-vs-name alternatives.

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 only 17%, and the description compensates by mapping each action to its valid parameters, marking optional ones with '?' (e.g., sync(dry_run?, confirm?, prune?)). This adds clear meaning beyond the raw schema. However, it omits the name-based alternatives (project_name/environment_name) present in the schema, leaving minor ambiguity.

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 opens with 'Local manifest cache CRUD and sync/diff for .coolify/manifest.json', naming exactly the file/resource and the operation families. The action enumeration (get, upsert, set, remove, clear, sync, diff, audit) gives specific verbs and distinguishes this from sibling tools like resource or deployment by scoping it to the local manifest cache.

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 usage by targeting the local manifest cache, but it lacks explicit 'when to use' or 'when not to use' guidance relative to sibling tools. The action signatures and safety note provide context, but there is no direct statement like 'use this for cache-only operations' or 'use resource for remote operations'.

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