Packages needing attention

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: the exact aggregation semantics behind 'needs attention', the scale warning for unfiltered queries, and the non-obvious fact that maintainer/team queries also surface canMerge PRs. It stops short of describing ordering or result shape.

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?

Two sentences, front-loaded with the definition before the scoping rules, with no filler. The second sentence is dense and packs several conditions (maintainer vs team vs list, canMerge) into one clause, which costs a little readability but every element is load-bearing.

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 6-parameter, zero-required, complex aggregation tool with no output schema, the description covers what is counted, how scope changes with filters, and the scale caveat. What is missing is anything about result ordering or the shape of a returned package entry, which an agent may want when composing downstream calls.

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 the baseline is 3 and the schema already documents kind, list, team, limit, platform, maintainer. The description still adds cross-parameter meaning the schema cannot: that maintainer/team/list are mutually alternative scoping dimensions and that maintainer/team additionally triggers canMerge results.

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 gives a precise definition of the resource: packages that need attention as the nixkeeper dashboard counts them, enumerating the qualifying categories (failing build, outdated, vulnerable, backport). This rescues a fairly vague tool name. It does not explicitly route the agent away from subset siblings like build_failures or vulnerabilities, so it stops short of full sibling 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 explains the two operating regimes clearly: without maintainer/team/list the scope is all of nixpkgs (thousands, narrow with kind), and with a maintainer or team the result also includes mergeable PRs (canMerge). That is concrete when-to-use context. It never names an alternative sibling tool to use instead, so no explicit exclusions.

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