deconvolve_data

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is externally known. However, the description adds no behavioral transparency beyond the basic operation—it does not mention overwriting previous results, requiring pre-loaded reference data, compute time, or other runtime effects.

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 compact and well-structured: one sentence of purpose, one sentence of parameter pointers. It is front-loaded with the core purpose and avoids unnecessary elaboration, making every sentence earn its place.

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 high complexity (8 deconvolution methods and many method-specific parameters), the description is minimal but not fatally incomplete because the schema and annotations carry substantial detail. Still, it lacks guidance on method selection, data prerequisites, or expected outcomes, leaving the agent to rely heavily on structured fields.

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 compensates for the 0% schema coverage by explicitly naming the effectively required trio: method, cell_type_key, and reference_data_id. This goes beyond the schema, which only marks cell_type_key as required. However, it does not explain the meaning of each parameter or how to choose methods, deferring entirely to DeconvolutionParameters.

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 starts with the specific action verb 'Deconvolve' on 'spatial spots' and clearly states the outcome: 'estimate cell type proportions.' This uniquely distinguishes the tool from siblings like analyze_spatial_statistics or identify_spatial_domains, which have different analytical goals.

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 usage when cell type proportion estimates are needed, but it provides no explicit when-to-use/when-not-to-use guidance or alternatives among sibling tools. The only additional guidance is a list of required parameters, which is more about invocation than usage context.

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