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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds value beyond those by disclosing the visibility scoping (org totals vs only the runs the caller can see) and the 7-day failure window, which materially affects how results should be interpreted. It stops short of describing response shape or refresh/freshness behavior, so not a 5.

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?

Three sentences, no filler, and the most important content (what is counted, including the 7-day failure window) is front-loaded. The routing hint and plan gate follow in order of decreasing importance.

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 input parameters and no output schema, the description must carry the full burden of saying what comes back, and it does: total/active workflow counts plus total and failed run counts over a stated window. It also discloses the consumer (dashboard widget) and the plan prerequisite, leaving no obvious gap for an agent.

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 for the description to clarify beyond confirming the counters are not filterable, which it effectively does by directing filtering to sibling tools.

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 specifies exactly what is counted: org-wide total and active workflows, plus caller-visible run totals and failures over the last 7 days. That is a specific verb+resource statement ('workflow counters') with explicit scope qualifiers, and it is clearly distinct from list_workflows/list_workflow_runs.

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 names the alternative tools explicitly ('PREFER `list_workflows` / `list_workflow_runs` for filtering') and states the condition that selects them, so the negative case is unambiguous. It also discloses the plan gate (automations PRO+), which is a real usage prerequisite an agent must check before calling.

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