transform_to_nm3_chunked

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

No annotations are present, so the description carries the full burden. It mentions chunked output but does not disclose behavioral traits like whether the tool is destructive, the need to later assemble chunks (given sibling assemble_chunks), or any side effects of caching/streaming parameters.

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?

Description is a single, front-loaded sentence that conveys purpose and benefit efficiently. It is concise without unnecessary words, though could be slightly expanded for clarity.

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?

Despite the tool having 7 parameters and no output schema, the description is minimal. It does not explain the chunking mechanism, how results are returned, or the relationship with sibling tool assemble_chunks. This leaves the agent with insufficient context to use the tool effectively.

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 already documents all parameters. The description adds no extra meaning beyond the schema; for example, it does not clarify how 'chunked output' relates to the parameters or the output process.

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 action (transform), input (markdown), output format (NM3 with chunked output), and the problem it solves (prevents truncation for large docs). It distinguishes from sibling transform_to_nm3 by mentioning chunked output.

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?

Implies usage for large documents to prevent truncation, but does not explicitly state when to use this tool vs alternatives like transform_to_nm3, nor when not to use it. No exclusions or alternative tool names are provided.

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