schedule_deployment

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

With no annotations, the description carries the full burden but only discloses that execution is deferred ('for future execution'). It does not reveal whether schedules can be canceled, whether inputs are validated at schedule time or execution time, whether recurrence is supported, or what response to expect (no output schema). The schema hints at mutually exclusive snapshot/versions and recurrence patterns, but the description itself adds almost no behavioral context.

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 single sentence is maximally efficient with zero waste and front-loads the verb. For an 8-parameter tool, though, the brevity reflects under-specification rather than crafted conciseness, so it does not earn a 5.

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 tool with 8 parameters, 4 required, mutually exclusive parameter groups, and no output schema, one sentence is insufficient. The description omits what the tool returns, how it differs from create_deployment_trigger, and any caveats about scheduling (e.g., that snapshot and versions are alternative ways to specify content). The rich schema does not compensate for missing tool-selection and outcome context.

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%, so the schema already documents every parameter thoroughly, including ID-not-name requirements, date formats, the recurrence enum, and the snapshot-versus-versions exclusivity. The description adds no parameter-level information, which is acceptable under the baseline-3 rule but contributes no additional insight beyond the 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?

States a specific verb ('schedule') and resource ('deployment') with the qualifier 'for future execution', which separates it from immediate-deploy siblings like deploy_snapshot_to_environment and deploy_component_versions. However, it does not differentiate it from create_deployment_trigger, whose name also implies scheduling future actions, leaving ambiguity about which scheduling tool to pick.

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 gives no guidance on when to choose this tool over create_deployment_trigger, deploy_snapshot_to_environment, or deploy_component_versions. No exclusions, triggers, or alternative-selection conditions are stated; an agent must infer the use case from the tool name alone.

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