measure_profile_length

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it requires an existing profile line, what units are returned, or any other behavioral trait beyond the basic measurement purpose.

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 with no filler or redundant clauses. It is appropriately sized for a simple one-parameter measurement tool.

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 one-parameter measurement tool with no annotations and no output schema, the description is too incomplete. It does not clarify the return value, units, or how the profile_line_id is obtained, leaving important context for the agent to infer.

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?

With one parameter and 0% schema description coverage, the description should compensate by explaining the expected profile_line_id format or source. It only repeats the concept of a profile line/transect and adds no syntax, format, or constraint details beyond what the parameter name already implies.

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: measuring the length of a profile line or transect. It distinguishes this from generic length or distance measurement by naming profile lines/transects, but it does not explicitly differentiate itself from sibling tools like measure_distance or get_curve_length.

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 says what the tool does but gives no when-to-use guidance, no conditions for selecting it over alternatives, and no exclusions. An agent must infer that it should be used for profile lines rather than other measurement tools.

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