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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds a genuine domain fact ('every publicly listed job is escrow-backed'), but says nothing about pagination, the limit cap, or result shape. Adds some value on top of annotations, not a lot.

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?

Two short sentences with the action front-loaded; nothing is padded or buried. The escrow sentence is slightly tangential but brief enough to earn its place as domain context.

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 read-only list tool with no output schema, the description covers safety implicitly via annotations but leaves the returned fields, ordering, and pagination behavior unstated, and only half the parameters are addressed. Adequate but with clear gaps.

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 the description must compensate, and it only partially does: it discloses the default status of 'open', which the schema's enum does not state. The limit parameter, its 1-50 range, and the meaning of the other enum values (claimed, in_review, complete, all) are left unexplained.

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 verb and resource: 'List paid jobs on Moonsox Desk.' This clearly differentiates a collection listing from the single-job sibling desk_get_job, though it never names that sibling explicitly. The scope qualifier 'paid' and the default status add useful precision.

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 gives no when-to-use or when-not-to-use guidance and names no alternative. '(default: open)' is a parameter default, not routing guidance, so an agent must infer on its own whether to call this versus desk_get_job or desk_starter_job.

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