entity_length

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

With no annotations, the description discloses the key behavioral trait of returning area for closed entities. It does not mention error handling, units, or behavior for unsupported entity types, which would be needed for full transparency.

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, front-loaded sentence that conveys the essential purpose without any waste. It lists supported types compactly.

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 single-parameter query tool with an output schema, the description provides adequate context by listing supported entity types and the area behavior. Slight gaps remain around unit/error behavior, but they are not critical for basic invocation.

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 schema has 0% description coverage and the description does not explain the 'handle' parameter beyond implying it identifies a curve. An agent would need to infer that 'handle' is an entity identifier from context.

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 the tool computes length (and area if closed) of a curve, listing specific entity types. This is a specific function with clear scope, though it doesn't explicitly differentiate from sibling tools like entity_points.

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 applicable entity types (line, arc, circle, polyline, spline) imply when to use the tool. However, there is no explicit guidance on when not to use it or which alternative to prefer for non-curve entities.

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