cf_restage

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

No annotations, so the description carries full burden. It says staging re-runs without code changes, which is useful, but doesn't state whether this disrupts running instances, requires a target/org context, or is reversible.

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 tight sentence with the clarifying parenthetical front-loaded after the verb. 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?

For a mutation-adjacent operational tool with no annotations and no output schema, the description omits disruption semantics, required context (org/space/target), and differentiation from cf_restart. Too thin given the deployment 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 coverage is 100% and the single parameter appName is fully described in the schema. The description adds no parameter details beyond that, so baseline 3 applies.

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 (restage) and resource (application), and the parenthetical clarifies it means re-running staging without code changes. It doesn't explicitly distinguish from cf_restart, a close sibling, but the mechanism (staging) is clear.

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?

No when-to-use guidance, no mention of prerequisites, and no distinction from cf_restart or cf_push despite their adjacency. The agent must infer when restaging is appropriate versus a restart or redeploy.

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