preference

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

With no annotations at all, the description carries the full burden and does meaningful work: it declares owner_quote as required for 'add', states that domain limits the preference to one domain with empty meaning everywhere, flags 'retire' as owner-only, and discloses the downstream effect that every brief shows the active ones. It stops short of covering reversibility, conflict behavior, or error conditions, which keeps it out of the top band.

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 opens with a one-line frame ('Owner preferences layer') then front-loads the two actions with their parameters. It is dense and largely waste-free; the parenthetical '(owner only)' and the closing note on brief visibility each earn their 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 six-parameter mutation tool with no annotations, no output schema, and zero schema coverage, the description covers most of the ground but leaves task_id entirely unexplained and gives no sense of what a call returns or mutates. It is adequate but has a visible hole on a tool where structured fields provide no backup.

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 0%, so the description must compensate, and it does for five of six parameters: action, text, owner_quote (marked required), domain (with the empty-means-everywhere semantics), and item_id. The task_id parameter is never mentioned, and the valid action values are only discoverable by reading the prose rather than an enum.

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 names the resource (an owner preferences layer) and specifies two distinct operations with their verbs: action='add' records a preference, action='retire' ends one by item_id. It is clear what the tool does, though it never explicitly contrasts itself with siblings like 'brief' or 'create_note', so an agent must infer the boundary.

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?

It implies when each action applies ('add' to record how the owner wants work done, 'retire' to end one) and adds a real constraint that retire is owner-only. There is no when-not guidance and no explicit routing to an alternative tool, so usage is implied rather than spelled out.

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