sc_deploy

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. It mentions alpha status and a dry_run constraint, but does not disclose side effects such as record_history writing to a local database, permissions, or return behavior. The phrase "execution requires dry_run=true" is also ambiguous because dry_run=true means no execution per the schema.

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?

The description is two compact sentences with no wasted words, and the core purpose is front-loaded before the alpha constraint.

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?

The schema fully documents all five parameters, and the description adds the important alpha/dry_run limitation. However, with no annotations and no output schema, the description omits enough behavioral context (side effects, return values, alternatives) that the definition is only minimally complete.

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 100%, so the parameter meanings are already documented in the input schema. The description only repeats the dry_run requirement and adds no syntax, format, or interaction details beyond what the schema provides.

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 states a specific verb and resource: "Build a safe deployment plan." It distinguishes the tool from an actual deployment execution, and the alpha-only note further narrows scope. However, it does not explicitly differentiate itself from the sibling sc_deploy_status tool.

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 gives a constraint ("Alpha only: execution requires dry_run=true") but no guidance on when to use this tool versus alternatives such as sc_deploy_status. There is no when-to-use or when-not-to-use context.

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