provision_resources

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

No annotations are provided, so the description should carry behavioral disclosure. It does mention one failure mode (missing neptune.json), but does not disclose side effects (e.g., creating/modifying cloud infrastructure), required permissions, or whether the operation is asynchronous. This is a significant gap for a provisioning tool.

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?

Two sentences, front-loaded with purpose and a useful error condition. No wasted words or redundant 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?

Given the output schema exists, return values are covered. However, the description fails to explain how the path parameter relates to the working directory, and does not clarify whether provisioning is immediate or requires later status checks (siblings include wait_for_deployment and get_deployment_status). The description feels incomplete for a tool that likely triggers infrastructure changes.

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 (schema coverage 0%). The description never mentions the parameter and instead references the 'working directory' and 'current project', potentially confusing the path parameter's role. It adds no value beyond the schema's bare type declaration.

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 verb (provision), resource (cloud resources), and scope (current project as per its configuration). It distinguishes itself from siblings like deploy_project (deploy vs provision) and add_new_resource (provision all vs add one).

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 gives context that the tool works with the current project's configuration and will error without a neptune.json file, implying when to use it. However, it does not explicitly state when to use this tool over alternatives or any exclusions.

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