Construction: XLine (infinite reference)

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

The description discloses that the line is infinite and placed on the CONSTRUCTION layer, which the annotations (destructiveHint=false) do not fully convey. It also hints at a temporary nature ('scaffolding') and a required cleanup step. This goes beyond the basic safety hint, providing important behavioral context.

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 two sentences long, with the core action front-loaded. Every clause earns its place—the scaffolding note and cleanup instruction are crucial without adding bloat. Highly efficient.

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 simple creation tool with a complete schema and annotations, the description is almost fully sufficient. It explains the purpose, usage, and cleanup requirement. The only missing piece is a mention of the output schema or return value, but that is covered by the output schema presence.

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?

The input schema already has 100% coverage with descriptions for all parameters (x, y, layer, angle_deg). The description adds minimal extra semantics beyond what the schema provides. Baseline 3 is appropriate since the schema handles the heavy lifting.

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 states a specific verb and resource: 'Create an infinite construction line on the CONSTRUCTION layer.' It also differentiates from siblings like construction_clear by mentioning scaffolding and the need to call it before finalize. The purpose is unambiguous.

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 clear context on when to use the tool: 'Use as scaffolding; call construction_clear() before finalize.' It implies this is not the final entity creation tool, but it does not explicitly mention alternatives like entity_create_line or state when NOT to use it. The usage guidance is strong but not exhaustive.

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