integrate_samples

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

Annotations (readOnlyHint=false) indicate mutation, but the description does not elaborate on side effects, computational cost, or required permissions. It does not mention GPU usage for 'scvi' method, although that is in the schema.

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 concise with a one-line intro and two argument lines in a clean structure. It is front-loaded and easy 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?

Given the complexity (nested parameters, output schema present), the description covers the basic purpose and arguments. However, it omits context like required preprocessing steps, data format assumptions, and what the unified dataset entails (e.g., new object or modification).

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 description lists the two parameters and hints at the nested params' content (method, batch_key, n_pcs, etc.). This adds some value over the schema, which lacks descriptions for top-level parameters, but the detailed schema already covers the nested object well.

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 (integrate), the resource (spatial transcriptomics samples), and the outcome (unified dataset). It is specific and distinct from sibling tools which focus on analysis rather than integration.

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?

No guidance is provided on when to use this tool versus alternatives like compare_conditions or preprocess_data. There is no mention of prerequisites or scenarios where integration is appropriate.

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