evidence_unset_label

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does tell the agent that other labels are preserved, which is useful, but it does not disclose permanence, required permissions, behavior with nonexistent labels, or potential side effects. For a mutation tool, this is a significant gap.

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 one short, front-loaded sentence with no filler. It communicates the action, object, and key behavior without wasting tokens.

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 schema is sufficiently rich and an output schema exists, so an agent can assemble a valid call. However, the definition is not fully self-sufficient because it fails to disambiguate from evidence_unset_labels and lacks behavioral safety context in the absence of annotations.

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?

The schema already documents all 100% of parameters, including the evidence name, record identifiers, and labels_to_remove array, so the baseline is 3. The description adds little beyond the schema's own wording, and that is acceptable given the high schema coverage.

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 the verb 'Remove', the resource 'specific label(s)', and the scope 'from a record, keeping the rest', which clearly conveys what the tool does. However, it does not differentiate this singular tool from the sibling evidence_unset_labels, which sounds like the same operation.

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?

There is no guidance about when to use this tool versus alternatives such as evidence_set_label or evidence_unset_labels. The description implies a removal use case but never states conditions, exclusions, or when the plural sibling would be preferred.

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