update_a_pipeline

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds 'Idempotent' and 'Modifies an existing record in place', which are consistent but not new. No additional behavioral details like permissions, error handling, or side effects beyond annotations.

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?

Description is relatively short but contains redundancy ('Update a pipeline' appears twice). The structured parts (emoji, HTTP method, resource) are front-loaded. Could be more concise by removing the duplicate sentence.

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?

No output schema is provided, and the description does not mention what the response contains. For a 2-parameter tool with nested body, additional context about return value or error handling would be helpful.

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?

Input schema has 100% description coverage for all parameters, including nested fields. The description does not provide any extra parameter information beyond what the schema already documents.

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 tool updates a pipeline, with the verb 'update' and resource 'pipeline' explicitly mentioned. It also includes the HTTP method and endpoint. However, it does not differentiate from sibling tools like 'create_a_pipeline' or 'delete_a_pipeline' beyond the verb.

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 explicit guidance on when to use this tool versus other update tools (e.g., update_a_deal_stage, update_a_deal_new). No prerequisites, when-not-to-use, or alternative tools are mentioned.

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