adjust_pipeline

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Adjust' implies mutation, but there is no mention of side effects, permissions, reversibility, or what changes occur. The description is too minimal for a mutation tool.

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 description is a single sentence that is front-loaded with the purpose. No redundant text. However, it could include more detail without becoming verbose.

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?

Given the tool has two required parameters (one nested object), an output schema, and 10 sibling tools, the description is too brief. It fails to explain how feedback tags adjust the pipeline, what the output contains, or any constraints. The existing output schema partially compensates, but the description is still incomplete.

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 0%. The description only names the parameters (pipeline, feedback_tags) but does not explain their structure or allowed values. For example, what is the format of feedback_tags? What properties does the pipeline object need? The output schema exists but does not help parameter 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 clearly states the verb 'adjust' and resource 'pipeline', and specifies it uses 'structured preview feedback tags' as input. However, it does not differentiate from sibling tools like 'recommend_pipeline' or 'update_pipeline' (if any), and the meaning of 'adjust' could be more specific.

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?

Usage context is implied: use when you have feedback tags from previews. There is no explicit guidance on when to prefer this over siblings like 'validate_pipeline' or 'explain_pipeline', nor any exclusions or prerequisites.

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