cm_update_segment

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

The description discloses that it replaces rule groups, which is a key behavioral trait. However, it does not elaborate on other behaviors such as idempotency (already indicated by annotation) or potential side effects like required permissions or impact on existing subscriptions. The description adds some context beyond annotations but is not comprehensive.

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 a single, clear sentence with no unnecessary words. It front-loads the action and scope, making it efficient for an AI agent to parse.

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 tool is simple with three required parameters and no output schema. The description covers the essential inputs and actions. It could briefly mention that existing rule groups are fully replaced (not merged) to enhance completeness, but overall it suffices.

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 input schema has 100% description coverage for all three parameters. The description reiterates the two main parameters (title and rule groups) but does not add deeper semantics, such as constraints or relationships between parameters. Baseline 3 is appropriate given 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 clearly states the verb 'Update' and the resource 'segment', specifying that it updates the title and replaces the rule groups. This distinguishes it from sibling tools like 'cm_add_segment_rulegroup' (which adds) and 'cm_clear_segment_rules' (which clears).

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?

The description implies when to use this tool (to update a segment's title and all rule groups), but does not explicitly state when not to use it or compare it to alternatives like 'cm_add_segment_rulegroup' for additive changes. More guidance on selecting this over siblings would improve clarity.

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