Setell add job context

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

The description discloses that the tool is a mutator (creates an Artifact row), aligns with annotations (readOnlyHint=false, destructiveHint=true), and adds behavioral context: the notes are private to the operator, feed the next quote draft, and content must not be summarized away. No contradiction with annotations.

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 sentences: core action with examples, storage behavior, usage guidance. Front-loaded and every sentence adds value. No redundancy or 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 3-param mutator with no output schema, the description fully covers purpose, behavioral impact, parameter nuances, and context alternatives. No missing information needed 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?

Adds meaning beyond schema: jobId suggests finding via setell_find_jobs, label becomes artifact filename, content advises preserving wording. Schema coverage is 100% but description enriches each parameter with practical usage hints.

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 tool attaches freeform scoping notes to a job, distinguishing it from the sibling 'setell_save_customer_memory' which stores durable customer facts. It uses specific verbs like 'attach' and 'store' and specifies the resource as 'scoping notes to 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?

Explicitly states 'Use when the operator narrates field notes' and 'Do NOT use for durable facts about a customer relationship (setell_save_customer_memory)', providing clear when-to-use and when-not-to-use with an alternative tool name.

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