Open nixpkgs PRs

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: the data is digest-derived and refreshed hourly, and the values are the digest's own judgements rather than raw GitHub state. It does not discuss pagination or result ordering beyond what the schema says.

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?

Front-loaded with the verb and resource, then the return semantics. It is one long colon-and-parenthetical sentence, which is dense but every clause carries information; only the trailing 'maybe its fix' aside is loose.

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 12 optional parameters and no output schema, the description does useful work by naming the result fields the caller will receive (buckets, state, merge-bot eligibility, duplicate flags, Hydra failures). Combined with annotations covering read-only behavior, an agent has enough to call it correctly.

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 schema already documents all 12 parameters including enum meanings. The description largely restates those same lists (buckets, merge bot) and only mildly enriches the concept of 'state' as a comparison with current nixpkgs. Baseline 3 applies when the schema carries the load.

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 and resource — 'Search nixpkgs' open pull requests' — scoped to the hourly PR digest, and enumerates the judgement fields it returns. It is clearly distinct from siblings like issues or find_packages by resource, though it never names an alternative explicitly.

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?

Usage is only implied: the parameter list (bucket, state, can_merge, blocks_bot) suggests the triage scenarios it supports, but there is no explicit 'use this when / use X instead' guidance or statement of prerequisites. The agent must infer the intent from the field inventory.

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