integrate_samples

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

Annotations already indicate readOnlyHint=false, so the description does not need to repeat that it modifies data. However, it adds no further behavioral context (e.g., side effects, authentication needs, output nature). With annotations covering the basic trait, a 3 is appropriate.

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 short and front-loaded with the main purpose. The Args section is somewhat redundant given the schema, but overall it is efficient. One sentence is pure purpose; the other is just a parameter list.

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 tool's complexity (many integration parameters, multiple methods) and the existence of an output schema, the description should explain what the output is or how the integration works. It lacks any mention of return values, behavior of different methods, or prerequisite steps.

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 0% per context signal, yet the description only restates parameter names in a stub ('data_ids: List of dataset IDs to integrate, params: Integration parameters'). It adds no detail beyond what the schema property names imply, failing to compensate for low schema coverage.

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 ('multiple spatial transcriptomics samples'), and the outcome ('into a unified dataset'). This is specific and distinguishes from sibling tools that perform different analyses.

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 when to use this tool (when integration is needed), but no explicit guidance is given on when not to use it or how it compares to alternatives. Usage is implied by the purpose, but exclusions or prerequisites are missing.

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