visualize_data

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

Annotations flag destructiveHint=true and readOnlyHint=false, so this tool may have side effects, but the description only mentions visualization and parameters. It does not disclose overwriting behavior, file side effects, or any other consequences. This is not a direct contradiction, but the description misses important behavioral context.

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 purpose, followed by a pointer to the schema. The Args block is mostly redundant with the schema but remains concise and does not significantly bloat the description.

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 very large VisualizationParameters schema, the pointer to that schema is helpful, and the output schema covers return values. However, the description lacks workflow context, side-effect awareness, and guidance on how visualization relates to upstream analysis steps. It is minimally viable but has clear gaps.

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 schema itself is highly detailed with property descriptions, so the description does not need to duplicate that information. It usefully highlights plot_type and subtype as primary controls and points to the VisualizationParameters schema. However, the example 'genes' does not exactly match the schema property 'feature', adding slight ambiguity.

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 begins with a specific verb and resource: 'Visualize spatial transcriptomics data.' This clearly distinguishes it from sibling tools like load_data, preprocess_data, and find_markers. The added instruction to set plot_type and subtype further scopes the tool's functionality.

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 tells users to set plot_type and subtype and reference the schema, but it does not explain when to use this tool versus alternatives, prerequisites, or when not to use it. No exclusions or alternative tool references are provided.

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