delete_logs_config_pipeline

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

No annotations are provided, so the description carries full burden. It states it's a deletion tool, implying destructive behavior, but doesn't disclose critical traits like whether deletion is permanent, requires specific permissions, has confirmation steps, or returns any output. For a destructive operation with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 two sentences with zero waste: the first states the purpose, and the second clarifies the parameter situation. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 this is a destructive deletion tool with no annotations and no output schema, the description is incomplete. It lacks information on how the pipeline is specified (e.g., via ID in URL), what the response looks like, error conditions, or safety warnings. For such a tool, more context is needed to guide the agent effectively.

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 description explicitly states 'This endpoint takes no JSON arguments,' which clarifies that no parameters are required beyond what might be in the URL or context. With 0 parameters and 100% schema description coverage, the baseline is high, and this statement adds useful confirmation, though it doesn't explain how the pipeline is identified (e.g., via URL path).

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 action ('Delete') and the resource ('a given pipeline from your organization'), making the purpose specific and understandable. However, it doesn't distinguish this tool from other delete operations in the sibling list (e.g., delete_logs_config_archive, delete_logs_config_indexe), which would require mentioning it specifically targets 'logs config pipelines'.

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 on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing pipeline ID), when not to use it, or what happens after deletion. With many sibling tools including other delete operations, this lack of differentiation leaves the agent without usage context.

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