list_segments

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

No annotations are provided, so the description carries the full behavioral burden. It implies an unfiltered enumeration via 'every segment', but never states read-only behavior, side effects, ordering, or what 'reference run' means; the output schema covers return fields but not call behavior.

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?

A single sentence with no filler is appropriately concise, but the metaphor 'slope library' and unexplained 'reference run' make it cryptic rather than clearly front-loaded with an action.

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 zero-parameter list tool with an output schema, the description is almost sufficient: it signals complete enumeration and inclusion of reference-run intersection data. However, it does not clarify what 'reference run' means or how this differs from siblings like segment_history.

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 tool has zero parameters, so there are no parameter semantics to document. Baseline 4 is appropriate because the description need not compensate for any schema gaps.

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?

Identifies the resource (segments) and scope ('every segment'), but lacks an explicit verb and the phrase 'where the reference run meets it' is ambiguous. An agent can infer this is a list operation, but not precisely what a segment record represents.

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?

No when-to-use or when-not guidance is provided, and no alternatives are named among the many sibling tools such as segment_history. 'The slope library' weakly implies discovery, but the description does not say when to choose this over segment-focused siblings.

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