analyze_trajectory_data

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

Description says 'Infer' which implies analysis, but annotations indicate readOnlyHint=false (mutation). No behavioral details beyond annotations are added, creating ambiguity about side 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?

Very concise, but overly brief. Lists Args without explanations. While not verbose, it sacrifices clarity for brevity.

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 of trajectory analysis (multiple methods, parameters) and rich schema, the description is too minimal. It omits key context like method selection guidance or return values.

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?

Description lists parameter names but provides no additional meaning beyond what is in the input schema. The schema already documents nested parameters, so the description adds no value.

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?

Description clearly states the tool infers cellular trajectories and pseudotime ordering, using specific biological terminology. This distinguishes it from sibling tools like analyze_velocity_data or analyze_cell_communication.

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 on when to use this tool versus alternatives, no prerequisites or exclusions mentioned. The description simply states what it does without context.

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