Create pipeline schedule

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

The description does not contradict the annotations (readOnlyHint: false is consistent with a create operation), but it also adds no behavioral detail beyond what the annotations already declare. Nothing about what gets created server-side, duplicate handling, authentication requirements, or the side effects of registration is disclosed, leaving the burden of transparency entirely on absent structured metadata.

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?

While the single sentence is technically short and front-loaded, this is under-specification, not conciseness. The description is no more informative than the tool's name and fails to earn its place by conveying any new information.

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 complex tool with 7 parameters, a deeply nested inputs type, CRON expressions, and timezone handling. The output schema's existence relieves the description of documenting return values, but the description still fails to explain scheduling semantics, parameter constraints, or usage patterns. For a tool of this complexity, the complete lack of guidance is a significant 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?

With only 14% schema description coverage, the description was expected to compensate for the undocumented parameters (ref, cron, cron_timezone, inputs, active), but it remains silent on all of them. Even the essential CRON format and the meaning of 'ref' are left unexplained, forcing the agent to guess at proper values.

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 'Create a project pipeline schedule.' merely restates the tool name and title almost verbatim, adding only the word 'project.' It is essentially a tautology that provides the agent with no additional information about the operation's purpose or scope beyond what is already visible in the name.

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 provides no guidance on when to use this tool versus create_pipeline, run_pipeline_schedule, or update_pipeline_schedule. There is no stated context, no exclusions, and no mention of alternatives—a notable omission given the rich set of sibling tools for scheduling and pipeline operations.

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