cloud_pull_branch

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

No annotations are provided, so the description carries the full behavioral burden and largely fails it. It doesn't say whether pulling overwrites local work, how conflicts are resolved, whether authentication is required, or what the result contains; only the cloud-to-local direction is conveyed.

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?

A single short sentence with the direction stated up front and no filler. Its brevity is a virtue structurally, though the missing content is penalized elsewhere.

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 five-parameter, unannotated, no-output-schema mutation-adjacent tool, this description is far too thin. Nothing covers parameter roles, overwrite semantics, or return values, leaving the agent unable to invoke it correctly beyond supplying design_id.

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 20% — only 'remote' has any text, and that is just a default value. The description explains none of the five parameters (design_id, branch_id, branch_name, since_version_id), so an agent cannot tell whether branch_id and branch_name are alternatives or whether since_version_id enables incremental pulls.

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 names a direction (cloud to local machine) and a resource, but calls it a 'design' while the tool name and schema are about branches. With siblings like cloud_pull_feature_branch and cloud_pull_preset_branch in the same namespace, the description gives no basis for telling them apart.

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?

There is no when-to-use guidance, no prerequisites (signed-in account? existing local branch?), and no mention of the alternative pull tools or when a branch pull is preferred over cloning or pushing. The agent must infer usage entirely from the name.

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