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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. Beyond that the description discloses a genuine side effect not in the annotations: it mints a Trust job ticket (poster + caller, lane 'desk') unless jobId is supplied. It does not cover authorization, rate limits, or what happens on failure.

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 tight sentences with the primary purpose front-loaded, followed by the ticket-minting side effect and then the directed-job caveat. Dense but every clause adds information; no 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 5-parameter mutation tool with no output schema and 40% schema coverage, this is adequate but incomplete: it never says what the returned ticket is or what the caller does next with it, and two required parameters (taskId, botId) are undocumented anywhere. Description and schema together still leave 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 coverage is only 40% (session and payeePubkey described, taskId/botId/jobId not), so the description must carry weight. It does explain the pivotal jobId switch ('mints ... unless you pass jobId'), which is the key behavioral parameter, but leaves taskId and botId entirely 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 (claim) and resource (an open public Desk job, or a soft-pool slot), and explicitly contrasts public vs. directed/invite-only jobs, which separates it from siblings like desk_list_jobs or desk_get_job. The jargon ('soft-pool slot', 'lane desk') is domain-specific but the action is unambiguous.

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?

Gives a clear precondition for directed jobs ('need an Alert knock first') and a fallback pointer ('see Desk skill.md'), which is real when-to-use guidance. It does not name which sibling to use instead for listing/browsing jobs, so routing between desk tools is left partly implicit.

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