deploy_project

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

With no annotations provided, the description carries the full burden. It discloses that the tool builds an image from the Dockerfile and warns that all container data is lost if the task stops or is redeployed, recommending provisioned resources for persistence. This is significant and beyond what the schema alone would convey.

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 compact and well-structured: one short sentence for purpose, one for the prerequisite, one for the under-the-hood build, and a concise note about persistence. There is no filler or repetition; every sentence earns its place.

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 description covers purpose, prerequisite, build behavior, and data persistence, and an output schema exists to handle return values. However, the sole required parameter is left unexplained, which is a significant gap for a deployment tool that needs a specific path to function correctly.

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 only required parameter, neptune_json_path, is not mentioned at all in the description, and the input schema gives only its name and type with 0% coverage. The description adds no meaning or format guidance for this parameter, leaving the agent without enough information to provide a correct value.

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 starts with the specific action 'Deploy the current project' and adds the under-the-hood detail that it builds an image from the Dockerfile. This clearly distinguishes it from sibling tools like provision_resources, wait_for_deployment, and get_deployment_status.

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?

It explicitly states a strong prerequisite: 'This only works after the project has been provisioned using provision_resources.' It also gives a when-not by warning about non-persistent data and advising use of provisioned resources. However, it does not explicitly name alternative tools for status or monitoring.

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