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

Annotations already declare readOnlyHint=true/destructiveHint=false, and the description adds genuinely useful behavior beyond that: output is counts only with no log text or repository data, the returned shape is {health, patterns, register}, and the interpretation rule ("N failures, 0 lessons" reads RED). This is solid additive context for a read tool.

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 auth gating and core purpose are front-loaded, and the detail is dense but mostly earns its place. It reads somewhat as a run-on sentence, but it is appropriately sized for the number of facets it lists.

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?

For a status tool with no params and no output schema, the description covers the auth requirement, the data scope, the return shape, and how to interpret the health value. That is nearly complete; only the absence of sibling routing keeps it from the top mark.

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 per the rubric the baseline is 4. There is nothing beyond what the empty schema already conveys, but no semantic gap exists to fill.

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 states a specific resource and scope: tracking whether CI failures are converted into lessons, with enumerated facets (classified failures, lesson.pattern events, recurring candidates, unlearned failures). This is clear and distinctive, though it never names or contrasts a sibling tool such as gluecron_ci_queue_status, so it stops short of full differentiation.

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?

It gives a real prerequisite constraint ("Site admins only, needs an 'admin'-scoped token"), which is useful gating context. However, it offers no when-to-use vs alternatives guidance and no explicit exclusions relative to the many other CI/status siblings.

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