curate_queue

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

With no annotations, the description carries full burden. It explains the curation process, outcomes (KEPT/PARKED), reasons for parking, that nothing is discarded, and the return shape. It could be more explicit about side effects (e.g., whether it modifies the database).

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 description is well-structured into two paragraphs. Every sentence adds value, though it could be slightly more concise. It is front-loaded with the main purpose and then details.

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?

The description is thorough for a complex tool, covering process, outcomes, reasons, and return values. It compensates for lack of annotations and schema descriptions. With an output schema present, the description need not explain return format fully.

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 0%, so description must explain parameters. It does: 'up to `limit` queue entries with the given queue status' clearly defines both parameters. It also mentions default values. However, it does not enumerate possible status values.

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 clearly states the tool's purpose: 'Triage the discovery queue into a fit-ranked active set and a parked set.' It uses specific verbs ('curate', 'triage') and identifies the resource ('discovery queue'). It distinguishes from sibling tool 'list_queue' which only lists without curation.

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?

The description implies that this tool is used after discovery to perform curation, but it does not explicitly state when to use it versus alternatives like 'discover_jobs' or 'list_queue'. No when-not-to-use guidance is provided.

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