Загрузить CSV-файл сегмента (CRM-данные)

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

Beyond the annotations, the description discloses important behavioral traits: the two-phase creation flow, the uploaded status and id in the response, the need for subsequent confirmation, the 100-record minimum and 1 GB maximum size, and the creation rate limits (10/min, 100/hour, 500/day).

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 longer than average but every sentence contributes essential information: file format, constraints, two-phase flow, data source options, and quotas. It is front-loaded with the primary purpose and well-structured.

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 multi-phase tool with no output schema, the description covers all necessary context: input format, source selection, size limits, status semantics, next step, and rate limits. It is sufficiently complete for an agent to invoke correctly.

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 has 100% description coverage for all three parameters, including the 'exactly one' constraint. The tool description repeats this constraint but does not add new parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 tool creates a segment from a CSV file with CRM data, using a specific verb and resource. It also distinguishes itself from siblings by emphasizing the CSV format and the two-phase creation flow with confirm_segment.

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 gives clear context: this is the first step of a two-phase process, followed by confirm_segment. It also clarifies the data source must be exactly one of file_path or content. However, it does not explicitly contrast with the sibling upload_segment_file, so it lacks a direct when-not-to-use statement.

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