List Pickfix batches

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

readOnlyHint=true already covers the safety profile, so the description only needs incremental context. It delivers that by disclosing the default filter scope (queued + working), which the schema does not state and which materially affects what the agent receives.

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 short sentences, front-loaded with what is listed, then the default scope. No filler or redundancy.

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?

There is no output schema, so the description ideally would describe what a returned batch looks like and whether results are paginated. It covers scope but stops short of return-shape detail; for a simple one-parameter list tool this is adequate but incomplete.

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?

With a single optional parameter and 100% schema description coverage, the schema already carries the meaning. The description's mention of "queued and working" usefully links to two of the enum values, but adds no syntax or edge-case detail beyond the schema.

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 (List) and resource (feedback batches sent by the Pickfix extension) scoped to this repository, which is unambiguous. It does not differentiate itself from siblings like pickfix_status or pickfix_claim_batch, which could also surface batch information.

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?

"By default shows queued and working batches" implies the common usage and hints that the status parameter narrows it, but there is no explicit when-to-use or when-not-to-use guidance relative to pickfix_status or pickfix_claim_batch. Usage is inferable rather than stated.

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