put-crm-v4-associations-var-var-labels_labels

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

No annotations exist, and the description 'Update' discloses zero behavioral traits. It does not mention side effects, required permissions, reversibility, or any operational implications of the mutation.

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 extremely short but this is under-specification, not effective conciseness. It lacks all necessary context and fails to communicate the tool's purpose or behavior.

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?

With 5 parameters, no output schema, no annotations, and a one-word description, the tool is completely underspecified. It provides no meaningful assistance to an agent 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?

Schema description coverage is 100%, so the baseline is 3. However, the schema descriptions are largely generic placeholder-like ('string parameter'), and the tool description adds nothing beyond the schema. The baseline applies because the schema at least lists all parameters.

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 is simply 'Update' with no resource specification. It fails to state what is being updated and does not distinguish from sibling tools like delete or get labels. It is essentially a bare verb with no substantive content.

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?

No guidance is provided on when to use this tool versus alternatives. The description gives no context for appropriate usage, prerequisites, or exclusions.

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