conduyt_ai_task_segment_and_act

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

With no annotations, the description carries the behavioral burden and does well: it discloses that the operation is non-persistent, returns the matched count and what WOULD change, and that execution is restricted to human sessions. It stops short of describing all response details or error conditions, but the key safety and persistence behavior is explicit.

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 front-loaded with 'PREVIEW ONLY' and three sentences cover purpose, return behavior, and execution restriction without waste. Every sentence contributes to correct tool selection or behavior understanding.

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?

There is no output schema, so the description must explain return behavior, which it does by stating it returns the matched count and what would change without persisting. It could say more about preview response shape or limit interaction, but the core preview semantics are complete for safe 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 schema already documents filter fields, action variants, and the limit parameter in detail. The description summarizes the action types (add/remove tag, assign user, update field) but adds no substantive meaning beyond the schema, which meets the baseline of 3 when schema coverage is high.

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 a specific verb and resource: previewing contact segmentation by filter plus applying an action to the whole segment. It clearly frames the tool as PREVIEW ONLY and lists action categories, but it does not explicitly differentiate itself from sibling AI task tools such as conduyt_ai_task_import_and_enroll or conduyt_ai_task_pipeline_cleanup.

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 explicitly says when the tool can be used by agents: preview only. It also states when execution is not allowed: 'Executing this is intentionally restricted to a human session in the app; agent/API-key callers can only preview.' This is a clear when-to-use and when-not-to-use boundary.

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