conduyt_set_targets

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

With no annotations, the description does real work: it discloses that this is an upsert keyed on user/metric/period, that a value of 0 deletes rather than stores, and that targets not in the payload are left untouched. It stops short of stating atomicity/partial-failure behavior for a batch of up to 200 rows, which is the main residual risk for a mutation tool.

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?

One sentence, front-loaded with the action and the permission scope, with no filler. The layered parenthetical-ish clauses make it dense to parse but every clause (permission, replace semantics, 0 = delete, membership rule, 200 cap) carries a distinct constraint.

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 no-annotation mutation tool with no output schema, it covers permission, validation, delete-via-zero, batch cap and keyed replacement. The remaining gap is response behavior—whether the call returns per-row success/failure or fails wholesale—which an agent would need before sending a large batch.

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% at the top level, so the description must compensate, and it does: it explains that the single array parameter is a set of (user, metric, period) rows whose existing value is replaced, and restates the 0-removal rule at the call level. The metric/period enums themselves are only in the schema, not the description.

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?

Specific verb ('Set') and resource ('per-user targets') with the batch scope ('in one call') front and center. It clearly differs from the read-only sibling conduyt_list_targets, though it never names that sibling explicitly.

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?

States the authorization gate ('admins and owners') and the preconditions for use ('every user must be an active member'), which tells an agent when the call will be rejected. It does not explicitly contrast with alternates such as conduyt_list_targets for reading existing targets, so there is no named alternative routing.

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