dokploy_catalog

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

No annotations are provided, so the description carries the full disclosure burden, and it does add one real behavioral caveat: the snapshot may not match the installed version. However, it says nothing about pagination behavior despite limit/offset, no return shape, and no rate or caching characteristics, which is thin for a discovery tool with zero annotation coverage.

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?

Three short sentences, front-loaded with purpose and then the sequencing instruction; nothing is padded. It is slightly clipped to the point of being terse — the compatibility sentence is cryptic without context — but there is no waste.

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?

With no annotations, no output schema, and 0% parameter coverage, the description leaves the agent without return format, pagination, or per-parameter meaning. The version-compatibility warning is genuinely useful but does not compensate for the rest of the missing context.

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 0% across four parameters (limit, offset, search, endpoint), and the description explains none of them. It never clarifies that 'endpoint' filters to one entry or that limit/offset paginate results, so it adds nothing beyond the bare schema names.

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?

States a specific verb and resource: 'Discover supported Dokploy endpoints and exact JSON parameter schemas.' It also names the sibling it precedes (dokploy_call), so an agent can place it in the workflow. It stops short of 5 because it doesn't make clear whether it returns a full catalog or a single endpoint lookup, which the 'endpoint' parameter implies.

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?

'Use before dokploy_call' gives explicit, actionable sequencing guidance that no sibling tool states. There is no when-not guidance and no statement of what happens if you skip it or call dokploy_call directly, which keeps it below a 5.

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