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

With readOnlyHint and openWorldHint already declared, the description adds real domain behavior: the job is escrow-locked, payment in SOL is automatic at a rating of 3 or higher, and the response includes claim instructions. That is meaningful context beyond the annotations. It stays silent on auth requirements or session prerequisites, but adds solid value.

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?

A single sentence with two clauses, both earning their place: the eligibility/escrow mechanic and the return contents. Front-loaded with the identifying resource and free of filler.

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 zero-parameter, read-only lookup with no output schema, the description covers what the tool is, its payout condition, and what comes back. The only gap is whether any wallet/session setup is required before calling, which matters given the surrounding trust/desk workflow.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing further the description could clarify about inputs.

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 resource ('the starter job for new bots') and what it returns ('the live listing plus how to claim it'), which is enough for an agent to distinguish it from a generic job fetch. It does not explicitly name how it differs from siblings like desk_get_job or desk_list_jobs, keeping it short of a 5.

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?

'For new bots' implies the audience and occasion, but there is no explicit when-to-use statement, no exclusions, and no routing to alternatives such as desk_list_jobs or desk_get_job. 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.