get_deployment_status

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

No annotations are provided, so the description carries the burden. It does disclose that the tool 'will tell you about running resources' and 'the state of the service,' indicating a read-only informational nature. However, it does not mention potential side effects, authentication requirements, rate limits, or output specifics beyond the high-level statement.

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 concise sentences that immediately establish the function and key detail. Every word earns its place, with no redundancy or off-topic information.

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 gives a high-level purpose but lacks usage guidelines and parameter semantics. An output schema exists, so return-value details are not required, but for a tool with one undocumented parameter and no sibling differentiation, the completeness is moderate.

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 schema has 0% description coverage for the only parameter, neptune_json_path, and the description does not mention or explain this parameter at all. The agent has no guidance on how to specify the path, making the tool difficult to invoke correctly.

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's verb and resource: 'Get the status of the current deployment of a project and its provisioned resources.' It adds specific detail about running resources and service state, which distinguishes it from siblings like wait_for_deployment and get_logs.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks explicit context such as 'use this to check whether deployment is complete' or mention of not blocking, unlike the sibling wait_for_deployment.

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