catalog_request_catalog_item_instances

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true; the description adds only the HTTP endpoint and the catalog-item source. It does not disclose whether the request is queued for approval, what happens on duplicate deployment names, or how inputs map to the created resource — behavior an agent needs for a non-idempotent create.

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?

It is short and front-loaded, but the first two lines say the same thing ('Create a deployment' / 'Creates a deployment from a catalog item'), wasting the prime opening slot on repetition rather than on scope or constraints.

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?

For a non-idempotent, open-world mutation that provisions a deployment, the definition omits the things an agent most needs: approval/request semantics, naming-conflict handling, and how this differs from the several other deployment-creation siblings. With no output schema, nothing else fills that gap.

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 coverage is 100% and every body field (inputs, reason, version, projectId, deploymentName, bulkRequestCount) is documented in the schema itself. The description adds nothing about parameter meaning, so the baseline 3 applies.

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 verb+resource is concrete: it creates a deployment from a catalog item, and the POST path confirms the endpoint. It does not, however, distinguish this from siblings such as deployment_create_resource, iaas_create_deployment, or deployment_action_deployment_request, which an agent could plausibly confuse with it.

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 offers no when-to-use guidance, no prerequisites, and no named alternative. It never says whether the deployment name should be pre-validated with deployment_check_deployment_name or when to prefer a plain deployment creation call instead.

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