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

Annotations already declare read-only/non-destructive, and the description's 'Read-only' merely repeats that. What it does add is auth behavior—site admins get the extra `dashboard` block—plus precise metric definitions (e.g. runner_slow, compute_trigger firing conditions) that help interpret results.

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 a single dense run-on sentence enumerating dozens of return fields, with the auth-scope caveat buried mid-paragraph. It is neither front-loaded nor scannable, and several clauses ('each day', 'a cost only where...') are awkward filler.

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 field inventory is the only return-value documentation, and it is thorough, including per-field `source` provenance and admin-only sections. It still omits response shape/format details, but for a zero-parameter read tool it is close to sufficient.

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, so the baseline is 4. The description correctly implies no input is needed, and there is nothing parameter-related for it to clarify.

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 opening names the resource ('CI health') and pins it to concrete endpoints, so an agent knows it retrieves CI health metrics. However, it never uses a verb and never distinguishes itself from siblings like gluecron_ci_queue_status or gluecron_ci_executor, leaving overlap ambiguous.

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 guidance and no comparison to the many CI-related siblings. The only conditional information is the admin-scope gating of `dashboard`, which describes access rather than task selection.

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