create_logpush_job

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

Beyond annotations (which show mutability and non-idempotency), the description adds critical behavioral context: the human-approval gate and preview mode behavior. No contradictions with 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?

Two concise sentences: first states the core action, second details the critical confirm behavior. No wasted words, front-loaded with essential 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?

The description covers purpose and confirm gate but does not mention return values, error cases, or post-creation behavior. Given the complexity (8 parameters, no output schema), additional context would be beneficial.

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 coverage is 100%, so the description does not need to explain each parameter. It adds minimal extra meaning beyond the schema; the confirm gate is highlighted but that's also in the schema. Baseline score of 3 is appropriate.

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 the tool creates a Logpush job streaming a dataset to a destination, clearly distinguishing it from sibling create tools. It also clarifies the required confirm gate, adding nuance.

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 clearly indicates when to use with confirm:true for actual creation and without for preview. However, it does not mention alternatives or when not to use this tool (e.g., for editing or listing).

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