Start Chunked Genome Upload

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

Annotations are unremarkable (no readOnly, destructive, etc.). Description adds some behavioral context (streaming without loading into context) but omits details about session lifecycle, returned session ID, or failure modes.

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 sentences efficiently convey audience restriction and purpose, with no unnecessary words. The critical audience warning is front-loaded.

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?

Despite low complexity, the description fails to mention what the tool returns (e.g., session_id) and does not guide on required subsequent steps (e.g., upload_genome_chunk). The absence of output schema makes this omission significant.

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 coverage is 100% for the single parameter 'filename', with existing description 'Original filename (for logging only)'. The tool description adds no further semantic meaning beyond this.

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 starts a chunked upload session for programmatic MCP clients, using specific verbs and resources. It distinguishes from sibling tools like get_upload_command and load_profile.

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?

Explicitly specifies that it is for programmatic MCP clients only, not LLM agents, and directs LLM agents to alternative tools (get_upload_command + load_profile).

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