reading_import_part

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

The description discloses that the tool appends data, which is a mutation, but provides no information about side effects, error conditions, or behavioral constraints. Annotations offer no behavioral hints (e.g., no readOnlyHint or destructiveHint), so the description carries the full burden yet adds minimal detail.

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 concise (one sentence, 8 words), which risks being underspecified. While there is no wasted text, the lack of parameter or context information suggests it is too sparse to be maximally helpful.

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?

Given the complexity of a chunked import process and the lack of output schema or annotation richness, the description fails to situate this tool within the larger workflow. It does not indicate when in the sequence it should be invoked or what the expected result is.

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 three parameters with zero schema description coverage, and the description does not clarify their semantics (e.g., what 'uploadId' refers to, the role of 'index', or the expected encoding of 'dataBase64'). It adds no meaning beyond the schema field names.

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 action and resource: 'Append one base64 file part to an active chunked import.' It distinguishes from siblings like reading_import_begin, reading_import_finish, and reading_import_cancel by specifying that it appends a part to an already active import.

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 the tool is for use during a chunked import, but it does not explicitly state prerequisites (e.g., must be used after reading_import_begin and before reading_import_finish) or when not to use it. No alternatives or exclusions are mentioned.

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