line

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

With no annotations, the description carries the full burden of explaining side effects, but it only says blocks are drawn in a line. It does not disclose whether existing blocks are overwritten, how the weighted block array is resolved, or if endpoints are included.

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 a single, direct sentence with no filler. It front-loads the core behavior and is appropriately sized for a straightforward drawing tool.

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 mutating tool with no annotations and no output schema, this is incomplete: an agent is left to infer overwrite behavior, coordinate conventions, and how the block parameter's variants behave. The terse description does not provide enough context for confident invocation in a block-editing environment.

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%, so the description should compensate for the schema's silence, but it only glosses over the parameters as 'two points' and 'blocks'. It does not explain that block can be a single object or a weighted array, nor add meaning to the from/to coordinates.

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 action ('Draw') and a distinct resource ('straight line of blocks') between two endpoints, which separates it from sibling shape tools like fillBox, wall, and sphere. It clearly maps the main intent to the from/to/block parameters.

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?

There is no guidance on when to choose this tool over alternatives such as setBlocks, wall, or fillBox. The description only states what the tool does, not the conditions that make it the right choice.

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