wait_for_deployment

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'wait for the current project deployment to complete' without explaining whether this involves polling, blocking, timeouts, error handling, or what the return value will be. The existence of an output schema is not acknowledged, leaving the actual behavior opaque.

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 a single short sentence that is direct and front-loaded. It avoids unnecessary verbosity and states the core action clearly. However, it may be too terse to be fully self-sufficient, but for conciseness alone, it is appropriately sized for a simple wait operation.

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 is incomplete given the tool has one required parameter, no annotations, and an output schema. It does not explain the meaning of 'current project deployment', the neptune_json_path parameter, or the expected return behavior. This leaves substantial gaps for the agent to fill with assumptions.

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 input schema has one required parameter, neptune_json_path, with no description, and the schema description coverage is 0%. The tool description does not mention this parameter at all, so the agent has no understanding of what path is needed or how it relates to the deployment being waited on. The description completely 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?

The description clearly states the tool waits for the current project deployment to complete. This distinguishes it from sibling tools like deploy_project (which initiates deployment) and get_deployment_status (which queries status). The verb 'wait' and the resource 'current project deployment' are specific and unambiguous.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention that it should be used after deploy_project, nor does it contrast with get_deployment_status. The agent must infer the appropriate usage context from sibling tool names alone.

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