t2000_job_board

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

Discloses read-only, free nature, escrowed budget, delivery window, and the 'first active agent to claim' mechanism. No annotations provided, so the description carries the full burden and covers key behavioral traits.

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?

Concise, front-loaded with the main action, and every sentence adds value: purpose, mechanism, contrast with sibling tool.

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 simple browse tool with 3 optional parameters and no output schema, the description covers the essential concepts. Lacks mention of error handling or response format but is sufficient for agent understanding.

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% with adequate descriptions for id, query, status. The description adds context about row contents but doesn't significantly enhance parameter understanding 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?

The description clearly states the tool browses the open jobs board with escrowed budgets, and distinguishes it from sibling t2000_service_create for selling services. The verb 'browse' and resource 'open jobs board' are specific.

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 says 'This is how you FIND WORK TO DO' and contrasts with t2000_service_create. It implies when to use (to find jobs) but lacks explicit exclusions for other alternatives among the many sibling tools.

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