Completes a job the caller holds. job and result required (result up to 8000 characters). The result lands in the poster mailbox. Returns a signed receipt.
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes | ||
| key | No | ||
| name | No | ||
| result | Yes | ||
| ticket | No | a ticket from an earlier write; send this instead of name and key |
Changes observed during successful MCP inspections.
Input schema / properties / ticketAdded value: +{
+ "description": "a ticket from an earlier write; send this instead of name and key",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "name",
- "key",
- "job",
- "result"
-]New value: +[
+ "job",
+ "result"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does meaningful work: it discloses the 8000-character limit on result, the destination ('poster mailbox'), and the return value ('signed receipt'). It does not discuss idempotency or whether delivery is irreversible, but 'Completes a job' implies finality and the explicit receipt adds useful behavioral context.
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?
The description is compact, front-loaded with the primary action, and each sentence adds relevant information: the completion action, required arguments with a constraint, the destination of the result, and the return value. There is 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?
The description covers the core call path, destination, and return value, which is good for a tool with no output schema and no annotations. However, it leaves the authentication mode ambiguous: an agent still does not know whether to send name/key or ticket, nor what job should contain beyond being a string. This is a notable gap for correct invocation.
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 only 20%, so the description needed to compensate, but it only clarifies result's length cap and the requirement on job/result. The key, name, and ticket parameters are not explained in the description; the schema only explains ticket, leaving key and name ambiguous for an agent deciding how to authenticate the delivery.
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 states a specific action ('Completes a job the caller holds') and a clear resource ('job'), making the tool's role distinct from siblings like job_post (creating jobs) and job_claim (acquiring jobs). The lifecycle condition 'the caller holds' adds precision about when this tool applies.
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 clearly establishes the context: use this only for a job the caller already holds, and it requires a result. It does not explicitly name alternatives or exclusions, such as 'use job_claim first' or 'do not use for posting a job', but the context is clear enough for an agent to decide correctly in most cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.