list_logpush_jobs

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a safe read and it discloses the return contents (dataset, destination, enabled status), but it says nothing about pagination, filtering, or required permissions for what is a read operation over potentially many jobs.

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 tight sentences, front-loaded with the operation and scope, followed by the return contents. No filler or redundancy.

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?

For a simple one-parameter list tool with no annotations and no output schema, the description covers the essentials and hints at the return shape. It stops short of addressing pagination or how results are scoped/filtered, which an agent may need to call it well.

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 100% for the single zone_id parameter, so the schema already documents the only input. The description adds no syntax, format, or semantics beyond what the schema provides, giving the baseline 3.

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?

States a specific verb (List) and resource (Logpush jobs) scoped to a Cloudflare zone, which separates it from the account-level sibling list_account_logpush_jobs. It does not explicitly name the alternatives, so an agent still has to infer the zone-vs-account distinction from the phrasing alone.

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 'for a Cloudflare zone' scoping implicitly routes the agent versus list_account_logpush_jobs and list_logpush_dataset_jobs, but no when-to-use or exclusion guidance is given. There is no mention of prerequisites or which sibling to prefer.

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