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

With no annotations, the description carries the full burden, and it does add genuine context: jobs are Dirtsmith's own data needs, each job specifies deliverables and how it is checked, and there is a 500-call/30-day credit incentive. It nonetheless omits auth requirements, pagination, and result volume, which matter for a listing endpoint.

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 short sentences with little outright waste, but the leading 'Contractors:' audience label delays the action, and the incentive/payment-explanation sentence is promotional rather than selection-relevant.

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 correctly compensates by explaining what a returned job contains ('exactly what to submit and how it is checked'). It stops short of describing ordering, counts, or pagination, but covers the essential shape of the response.

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 a single enum parameter (open/all, default open), so the schema already documents the only input. The description adds no syntax or behavioral meaning beyond that, making the baseline 3 appropriate.

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 makes clear this surfaces open data jobs a contractor can perform, and 'open data jobs' implicitly conveys the default status. However, it never states the verb 'list' explicitly and doesn't mention the open/all filter, so an agent must infer that this is the retrieval endpoint for job listings rather than something like claim_job or submit_job.

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?

There is no explicit when-to-use guidance and no routing to siblings such as claim_job, submit_job, or check_credit, which are the obvious next steps in this workflow. The mention of earning a credit pass implies motivation but not selection criteria.

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