set_job_description

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

No annotations are provided, so the description carries the full burden. It discloses the main behavior (replacing the description), but does not mention consequences such as overwriting existing text, whether the job must already exist, or any permission requirements. It adds some context beyond the schema but lacks depth for a mutation operation.

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 two sentences with no filler. The first sentence states the action, and the second explains when it is useful. It is front-loaded and every word earns its place.

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 simple update tool with two string parameters and an output schema, the description covers the key aspects: what it does and when to use it. It does not explain error cases or side effects, but the output schema likely handles return values. The description is sufficient for this level of complexity.

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 0%, so the description must compensate for the bare schema. It implicitly explains that job_id identifies a saved job and description is the pasted full text. This adds meaningful context beyond the parameter names, though it could be more explicit about formats or constraints.

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 clearly states the action: 'Replace the description of a saved job with pasted text.' This uses a specific verb and resource, and it distinguishes itself from sibling tools like save_job (which adds a new job) and delete_saved_job (which removes a job).

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 a clear use case: 'Useful when the listing was saved from a feed with a truncated or empty description and you have the full text.' This provides context for when to use the tool, though it does not explicitly mention when not to use it or name alternative tools.

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