Extend Entity

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

Describes auto-selection of endpoint when end_x/end_y is None, raises on parallel lines, and version limitation. Annotations (readOnlyHint false, destructiveHint false) are consistent, and description adds behavioral detail beyond them.

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?

Two concise sentences that front-load the main purpose and add critical constraints. No superfluous words.

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?

Explains core functionality, constraints, and behavior for optional parameters. Does not mention the output schema or side effects, but these are less critical for a simple extend operation.

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 already fully describes parameters (100% coverage). Description adds minimal extra meaning beyond restating the auto-select behavior, which is already implied by default null values.

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?

Clearly states the action 'Extend target to meet boundary' with a specific verb and resource. Specifies LINE+LINE only, which distinguishes it from other tools like entity_trim or entity_fillet.

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?

Provides context by noting 'V1 supports LINE+LINE only' and 'Raises if parallel,' which guides when to use. Does not explicitly mention alternatives, but the constraints are clear.

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