data_generate_fetcher_script

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

The annotation readOnlyHint=true already establishes that the operation has no side effects. The description adds that the generated scripts include 'error handling and data processing', but this is vague and does not explain whether the tool returns code, writes files, or executes anything. No contradiction with annotations exists.

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 one sentence with the core action and object front-loaded: 'Generate Python scripts for fetching submatrix data'. There is no filler or repetition, and the added phrase about error handling and data processing earns its place with relevant context.

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?

With a full parameter schema, an output schema present, and annotations covering read-only behavior, the description covers the minimum needed to invoke the tool. However, it omits context about how the generated script relates to execution versus other data tools, and it lacks sibling differentiation, leaving some ambiguity for an agent deciding between tools.

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 100%, so the schema fully documents all six parameters. The description does not add meaningful detail about parameters, such as how script_type affects the output or what output_format options imply. It stays at the baseline of 3 given the complete 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 uses a specific verb 'Generate' with a clear resource 'Python scripts for fetching submatrix data', distinguishing it as a code-generation tool rather than a data-reading tool. It is clear about the deliverable, though it does not explicitly differentiate itself from siblings like data_read_submatrix or plot_generate_code.

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 such as data_read_submatrix, which actually reads data, or plot_generate_code, which generates visualization code. There are no use conditions, exclusion criteria, or scenario hints.

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