parse_large_plate_stream

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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions 'memory-safe stream' which hints at memory-efficient processing, but it does not disclose return format, validation behavior, error handling, or side effects. This is insufficient for a tool with no 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 one sentence, front-loaded with the key action ('parser') and resource. Every word contributes meaning ('memory-safe', 'stream', '96-well or 384-well'), with no redundant or verbose language.

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 absence of annotations and output schema, the description should provide a complete picture of what the tool does, how to use it, and what it returns. It lacks essential details such as input format specifics, output structure, and parameter explanation, making it inadequate for a complex parser tool.

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 0%, and the description does not explain the parameters at all. It does not describe the expected format of 'plate_layout_csv' or how 'format_wells' affects parsing. The description adds no value beyond the raw schema.

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 identifies the tool as a parser for 96-well or 384-well microplate layout string rows. It uses a specific verb ('parser') and defines the exact resource and format scope. This clearly distinguishes it from the analysis-focused sibling tools.

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 usage for large plate layouts via 'memory-safe stream', but it does not provide explicit when-to-use guidance, prerequisites, or alternatives. No mention of whether this should be used before analysis tools or when the input size warrants streaming.

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