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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without description help. The description contributes only a hint about returned content ('spec, pay and rules'); it says nothing about auth requirements, failure modes, or the fact that the session token is per-call only.

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 nine-word sentence with no filler, and the most important scope constraint ('one Desk job') is front-loaded. It is efficient, though arguably terse to the point of under-specification rather than ideal conciseness.

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?

With no output schema, the description carries some burden for describing the return, and 'full spec, pay and rules' is a reasonable if vague sketch. However, it leaves the required taskId semantics and the session-token requirement unaddressed in prose, which is a real gap for a tool whose only required input is undocumented.

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 only 50%: the session parameter is documented in the schema, but taskId has no description and only a regex pattern. The description never mentions either parameter, so it does not compensate for the undocumented taskId, leaving the agent to infer the 'task_' id format purely from the pattern.

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+resource ('Read a Desk job') and scopes it to a single job, which distinguishes it from the list-style sibling desk_list_jobs. It also previews the payload ('full spec, pay and rules'). It stops short of naming alternatives explicitly, but an agent can tell it is a single-item lookup.

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 phrase 'for one Desk job' implies retrieval of a single job by identifier, which is enough to separate it from desk_list_jobs or desk_claim_job by inference. There is no explicit when-to-use statement, no mention of prerequisites (e.g., needing a job's taskId first), and no named alternative.

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