Trim Entity

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

The description discloses that the cutter is treated as an infinite ray (implied extend mode) and that an error is raised if lines are parallel. This adds behavioral context beyond the annotations, which only indicate readOnlyHint and destructiveHint. The mutation aspect (trimming) is implied but clear.

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 brief and to the point. The primary action is stated first, followed by constraints (V1 limitation) and a note about the cutter behavior and error condition. No unnecessary sentences.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the essential behavior: what is trimmed, the parameters, supported types, and error conditions. No gaps are apparent.

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 provides descriptions for all 4 parameters, so schema coverage is 100%. The description adds context for keep_x and keep_y (a point on the side to keep) but does not add significant meaning beyond what the schema already states. Baseline of 3 is appropriate.

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 (trim), the resources (target and cutter lines), and the keep point. It specifies the supported entity type (LINE+LINE) and distinguishes from sibling tools like entity_extend and entity_fillet by describing the trim operation and its constraints.

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 notes that only LINE+LINE is supported in V1, which guides the agent on when this tool is applicable. However, it does not explicitly state when to use this tool versus alternatives (e.g., entity_extend) or provide a when-not-to-use scenario.

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