create_deployment

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

No annotations provided, so description details behavior: dry_run default creates preview, returns confirmation string, version_number must be >=1. Discloses the dry run vs actual mutation distinction.

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 plus args list; action is front-loaded. Some redundancy with 'Returns:' line, but overall efficient.

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?

Covers inputs and output well for a create tool. Missing prerequisites (e.g., existing script project) and auth requirements, but adequate given 5 params and output schema.

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?

With 0% schema description coverage, description thoroughly explains each parameter: user_google_email required, script_id, description, version_number constraint (>=1), dry_run default. Adds significant meaning beyond schema.

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?

Description clearly states 'Create an Apps Script deployment' with specific verb and resource, distinguishing it from sibling tools like update_deployment and delete_deployment.

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 on when to use this tool versus alternatives like update_deployment or list_deployments. Missing prerequisites or context for creation.

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