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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the description is not carrying the safety burden. It adds the scoping trait 'currently active jobs' and names the telemetry fields returned, but says nothing about pagination, ordering, or whether results are global or scoped to the caller.

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 with no filler or redundancy. The scope constraint ('currently active') and the payload contents are both stated in the first clause.

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 no output schema, the description does the right thing by naming what is returned (pipeline phase, telemetry status), but for a listing endpoint it omits result volume, ordering, and whether the list is bounded. Complexity is low and annotations cover safety, so it is adequate rather than complete.

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?

The tool takes zero parameters and schema description coverage is 100%, so there is nothing for the description to clarify. The rubric's baseline for a zero-parameter tool applies.

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 (currently active jobs) plus the two fields returned (pipeline phase, telemetry status). The word 'active' implicitly distinguishes it from list_jobs and the historical get_telemetry_logs, but it never names a sibling, so differentiation requires the agent's own inference.

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?

There is no when-to-use statement and no alternatives named. In a namespace containing get_job_telemetry, get_telemetry_logs, get_telemetry_stats, and system_telemetry, an agent gets no routing signal beyond the adjective 'active'.

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