cloudflare_worker_analytics

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

With no annotations, the description carries full burden. It discloses that the tool returns time-series data ordered by time and lists specific metrics. It does not cover potential side effects (none expected for a query), but it is reasonably transparent about behavior given the tool's read-only nature.

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, front-loading the purpose and then specifying return details. Every sentence adds value with no wasted words.

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 2 parameters with full schema coverage and no output schema, the description adequately explains what the tool returns (metrics, time-ordered). It is complete for a simple query tool, though it could mention that results are aggregated per script.

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%, so the schema already documents both parameters well. The description adds context about default/max values for 'limit' and ISO 8601 format for 'since', but does not substantially enhance 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 clearly states the tool queries Workers invocation analytics and returns specific time-series metrics (requests, errors, subrequests, CPU time percentiles). It uses a specific verb 'Query' and specifies the resource ('Workers invocation analytics'), effectively distinguishing it from sibling analytics tools like cloudflare_ddos_analytics.

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 explicitly mentions it is for Workers invocation analytics, which implies usage context. However, it does not explicitly state when to use this tool over alternatives (e.g., cloudflare_ddos_analytics), nor does it provide exclusions or when-not-to-use guidance.

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