transform_get_df

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

With no annotations, the description carries the full behavioral burden. 'Get' clearly indicates a read-only operation, and the description explains optional behaviors: matrix indexing via m and n, and including imaginary components via imag=true. It does not mention side effects or failure modes, but for a simple getter the behavior is adequately transparent.

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: two sentences with no fluff. It front-loads the core purpose ('Get a Transform dataset as a DataFrame') and then adds only the most relevant behavioral details. Every sentence earns 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?

For a straightforward getter tool with five schema-documented parameters, the description covers the essential purpose, return type, and key optional behaviors. It does not explicitly address the msb parameter, but the schema already documents it with a default. Overall, the description is sufficient for an agent to understand and invoke the tool correctly, though a note on when not to use it would improve completeness.

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 baseline is 3. The description adds some value by grouping m and n as matrix-indexing dimensions and mentioning imag=true, but it largely restates what the schema already says about individual parameters. It does not meaningfully deepen understanding of msb or transform_path.

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 states a specific verb and resource: 'Get a Transform dataset as a DataFrame.' It clearly identifies the output type and distinguishes this tool from siblings like transform_get_data by emphasizing DataFrame return. The matrix indexing mention adds further specificity without ambiguity.

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 use when a DataFrame representation of a Transform dataset is needed, but it does not explicitly state when to use this tool versus alternatives such as transform_get_data, input_get_df, or output_get_df. No when-not-to-use or alternative guidance is provided, so usage context remains only implied.

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