analyze_cell_communication

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

Annotations indicate destructiveHint and idempotentHint, but the description does not elaborate on potential side effects, whether the analysis modifies data, or any performance implications. No additional context is provided beyond the annotations.

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) but lacks necessary structure or detail for a complex tool with many parameters. It is minimal without being 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 tool's complexity (large parameter set, multiple methods), the description is woefully incomplete. It does not mention output types, method options, or any contextual information that would help an agent decide to use it.

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 does not explain any parameters. The schema contains many parameters with individual descriptions, but the tool description itself adds no param-level semantics. Since schema coverage in the description is 0% and the description fails to compensate, this scores low.

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 analyzes cell-cell communication and ligand-receptor interactions, which distinguishes it from sibling tools like analyze_spatial_statistics or analyze_enrichment. However, it lacks specificity about the analytical methods or outputs.

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 provides no guidance on when to use this tool versus alternatives, no mention of prerequisites, or scenarios where it is appropriate. It only gives a generic purpose.

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