query_logs_batched

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

With no annotations provided, the description carries the full burden and does disclose the meaningful non-obvious trait: rows are sampled per time bucket rather than taken from the newest lines only, so results are not a contiguous tail. However it says nothing about ordering, pagination, cost/rate limits, or permission requirements.

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 short sentences, zero waste, with the sampling behavior front-loaded ahead of the rationale. Everything stated earns its place.

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?

Adequate for a 6-parameter read tool, but with no output schema and no annotations the description should say more about the shape of returned rows and the relation between limit and per_bucket. The sampling intent is covered; the result contract is not.

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 baseline is 3, and the description genuinely adds meaning to the bucket parameters by explaining that output is a 'balanced slice across time buckets' — clarifying how bucket_minutes and per_bucket interact with the window. It still does not relate limit to per_bucket × bucket count.

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 and resource ('fetch a time-bucketed sample') plus the scope ('over a larger window'), and explains the distinguishing sampling behavior versus 'only the very latest lines'. It never names the obvious sibling query_logs, so an agent must infer the boundary itself.

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?

Gives a usage condition ('useful when logs are high-volume'), which is real but implicit guidance. It does not name query_logs or fetch_window as alternatives, nor state when to prefer those instead, leaving the sibling routing decision to the agent.

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