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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and the description's added burden is light. It contributes the fact that results are filter-driven and support full-text search, but says nothing about ordering, default window, or pagination beyond the schema's limit default.

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?

A single front-loaded sentence that leads with the verb and resource before listing filters, with no filler. It could be slightly sharper by grouping the filters rather than dumping them, but nothing is wasted.

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?

With eight optional parameters and no output schema, the description should ideally say what a log entry looks like and how results are ordered or truncated. It covers the input surface adequately but leaves the return shape and default result window unexplained, which is a meaningful gap for a log-query tool.

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 each of the eight parameters is already documented inline, establishing the baseline of 3. The description only restates the same filter categories (level, source, jobId, kernelId, time range, search) without adding syntax, combined-filter behaviour, or timezone/range semantics.

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 (query) and resource (structured logs) and enumerates the filterable dimensions, so the agent knows exactly what the tool retrieves. However, it does nothing to separate itself from near-neighbours like get_job_telemetry, get_active_telemetry, system_telemetry, or get_telemetry_stats, leaving ambiguity in a crowded telemetry family.

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?

Pure capability statement with no guidance on when to prefer this over the sibling telemetry readers or emit_telemetry. No exclusions, prerequisites, or situational triggers are provided, so the agent must infer usage from the name alone.

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