logs_pipelines

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

No annotations are provided, so the description bears full responsibility. It discloses read-only mode blocking mutations and forwarding of unknown processor types. Yet it omits details on success/error responses, pagination for list/get, and the impact of deletion.

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?

Three concise sentences immediately state purpose and actions. Every sentence adds unique information with no redundancy, making the description efficient.

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 complexity (7 actions, 5 params, nested objects) and lack of output schema, the description should clarify return values and error patterns. It covers basic behaviors but leaves gaps about list/get outputs and reordering side effects.

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?

All 5 parameters have schema descriptions (100% coverage), achieving baseline 3. The description adds value by stating that config requires 'name and filter.query' and that processors are forwarded unchanged, plus explaining the verbose parameter. This enriches parameter understanding beyond the schema.

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 explicitly states 'Manage Datadog Logs pipelines (parsing & processor chains)' and lists all 7 actions (list, get, create, update, delete, reorder, get_order), clearly identifying the verb and resource. It distinguishes from sibling tools like logs_archives, logs_indexes, and logs by focusing on 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?

The description provides context: pipelines run sequentially, reorder changes downstream data, and mutations are blocked in read-only mode. However, it doesn't explicitly contrast with other logging tools or specify when to use this tool over alternatives like logs.

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