Delete pipeline schedule

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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds no additional behavioral context beyond what is destroyed, such as permanence, permission requirements, or effects on associated variables.

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?

A single, front-loaded sentence that immediately states the action with zero filler. Every word is purposeful.

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 simple two-parameter delete operation, the schema and annotations cover the basic inputs and destructiveness. However, the description lacks contextual details such as irreversibility or whether associated schedule variables are removed, making it minimally complete.

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 schema describes 'project' but leaves 'pipeline_schedule_id' undocumented, and the description adds no parameter-level meaning. The param name is inferable from the schema, but the description contributes nothing to clarify semantics.

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 states 'Delete a project pipeline schedule,' using a specific verb and resource. It clearly distinguishes this tool from sibling delete_pipeline_schedule_variable by targeting the schedule itself.

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 is provided about when to use this tool versus alternatives like update_pipeline_schedule or delete_pipeline_schedule_variable, nor are prerequisites or exclusions mentioned. Usage is only implied by the action.

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