Construction: XLine (infinite reference)

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

Annotations only provide destructiveHint: false. The description adds that the line is on the CONSTRUCTION layer and intended as scaffolding, which provides behavioral context beyond annotations. However, it does not detail what happens when the tool is invoked multiple times or how the infinite line behaves.

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 only two sentences, front-loading the core purpose and then providing a key usage guideline. No redundant information.

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 being brief, the description covers the tool's purpose, its intended use as temporary scaffolding, and how to clean it up. With an output schema present and simple creation semantics, this is complete for the agent's needs.

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 coverage is 100%, so the schema already documents all parameters. The description does not add any additional parameter semantics beyond what is in the schema (e.g., no explanation of x, y, angle_deg formats).

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 the action 'Create an infinite construction line' on a specific layer ('CONSTRUCTION'), distinguishing it from regular line creation tools like entity_create_line. The mention of 'scaffolding' and 'construction_clear()' further clarifies its role.

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 explicitly says 'Use as scaffolding' and instructs to call construction_clear() before finalizing, providing clear context for when to use this tool. It does not explicitly exclude other scenarios, but the guidance is sufficient for typical usage.

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