cloud_remote_list

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

With no annotations present, the description must carry the full burden. It does disclose the Kiln Pro entitlement gate, which is real operational context, but it says nothing about what a remote entry contains or what happens when no remotes are registered, and it never states the tool is a read-only listing.

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?

Only the first sentence describes the tool. The remaining two sentences are marketing copy about pushing and pulling design branches plus an upgrade URL, which does not help an agent decide how to invoke a zero-parameter list call.

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 zero-parameter read, the description covers what is listed and the entitlement requirement, which is close to sufficient. It omits any indication of return shape or empty-state behavior, and there is no output schema to fill that gap.

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 tool takes zero parameters, so the baseline is 4. Nothing in the description is needed to explain inputs, and nothing misleading is added.

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 first sentence gives a specific verb and resource: list all registered Kiln Cloud remotes. That distinguishes it from siblings such as cloud_list_remote_branches and cloud_list_remote_releases, though the description never names those siblings to make the split explicit.

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 'Requires Kiln Pro' line is a genuine gating condition for invoking the tool, but there is no explicit statement of when to choose this over the branch/release listing siblings, nor when not to call it.

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