onboarding_post_task_create_deployment

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the description adds nothing about side effects, permissions, or reversibility. In particular it never explains what 'update' does when an existing deploymentLink is supplied, which is the central behavioral question here. No contradiction with annotations, but no added value either.

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 same sentence appears twice and the raw endpoint path is appended as a third fragment, producing zero informational gain across three lines. Nothing is prioritized, and the redundant repetition crowds out the absent usage guidance.

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?

This is a non-idempotent write with a large nested body, no output schema, and multiple interacting fields (template, resources, createBlueprint), yet the description says nothing about return behavior, async processing, or the create-vs-update distinction. The rich schema partially compensates, but the description is far too thin for the operation's complexity.

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 description coverage is 100% and the nested body fields (deploymentLink, planLink, template, resources, createBlueprint) are documented inline, so the schema does the heavy lifting. The description adds no semantics of its own about the body, so 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 description names the resource (onboarding deployment plus associated resources) but hedges with 'create or update', leaving it unclear which operation this actually performs. It never distinguishes itself from close siblings like onboarding_post_deployment, onboarding_post_task_create_deployment_bulk, or onboarding_patch_deployment_by_id, so the agent cannot confidently choose 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?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives despite several near-duplicate siblings in the list. The only context is 'in the current organization' and a raw POST path, neither of which guides tool selection.

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