deploy

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is an external, mutating operation. The description adds the internal mechanism (runs deploy script or make deploy), which is useful, but says nothing about what the deployment destroys or overwrites, whether it is long-running, or what permissions it needs.

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, front-loaded sentence with no filler. The parenthetical is efficiently scoped to mechanism rather than restating the name.

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?

Although an output schema exists so return values need no explanation, this is a destructive, open-world operation with two undocumented required parameters and no stated side effects or prerequisites. The definition leaves too much for the agent to guess.

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 three parameters, including two required ones. The description never explains what project_path or target mean, and target in particular is entirely opaque with no enum or format hint, so it fails to compensate for the schema gap.

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 ("Trigger deployment for a project") and adds the mechanism (deploy script or make deploy), so the outcome is unambiguous. It does not distinguish itself from siblings like run_command or run_tests, which could plausibly also be used for deployment-style work.

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, and no named alternative. An agent cannot tell from the description whether deploy should be preferred over run_command for the same effect, which is the key routing decision among these siblings.

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