Bulk Triage

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

Discloses key behavioral traits: it applies status to all scanned board jobs matching filters, server selects jobs (no need for IDs), returns text, and recommends post-call action (call show_board). No annotations exist to contradict.

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 with no wasted words. First sentence gives purpose and example, second explains mechanism, third clarifies scope and provides follow-up instruction. Efficient and well-organized.

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 bulk operation with 5 params, no output schema, and no annotations, the description covers essential behavioral aspects (selection, return format, post-call step). Could mention error handling or rate limits, but not required for basic usage.

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 coverage is 100% (baseline 3). Description adds value by clarifying that `below_score`/`above_score` match only SCORED jobs (linking to `clear_jobs`), and implies that at least one filter is needed.

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 with a specific verb ('Triage') and resource ('board jobs'), and gives an example ('dismiss every scored job under 60'). It distinguishes itself from sibling 'clear_jobs' by noting the scoping to scored jobs only.

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?

Explicitly states when to use (bulk triage by score/source) and when to use alternatives ('use clear_jobs for un-evaluated ones'). Also provides a usage constraint: 'Provide at least one filter'.

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