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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds real downstream context the annotations cannot convey: newsletters and journeys follow the change, and 'entered a segment' journeys may newly trigger for contacts who now match. That consequence disclosure is valuable beyond the structured hints.

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?

Two short sentences, zero filler, and the core action is front-loaded ahead of the side-effect disclosure.

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 destructive nested-object mutation tool with no output schema, the description covers the main risk an agent must know (downstream effects on newsletters and journeys). It is slightly incomplete on partial-update semantics, but the schema carries the rules detail.

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 67%, with the nested rules object carrying a very detailed inline description of fields, operators, and date formats. The prose description adds nothing about parameters (e.g., whether omitting name leaves it unchanged or whether rules fully replace existing rules), so it only meets the baseline.

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?

States two specific operations (rename, replace rules) on a named resource, so the agent knows exactly what the tool mutates. It does not name a sibling or explicitly contrast with create_segment/list_segments, but the verb+resource combination is unambiguous.

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?

Usage is only implied: the description notes the two mutation modes but never says when to prefer this over create_segment, or what prerequisites (segment ownership, plan limits) apply. No explicit when-not guidance is given.

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