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 burden. It indicates the operation is read-only ('returns the list') but does not disclose potential pagination, sorting, or if the list could be empty. For a simple list endpoint, this is adequate but not rich.

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 sentence that concisely states the tool's purpose and parameter source. It is front-loaded with the main action and resource, and every word contributes meaning.

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?

The tool lacks an output schema, and the description does not specify the structure of the returned list (e.g., array of segment objects with IDs and names). Given the complexity (single parameter, simple list), a bit more detail on the response format would complete the picture.

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 has 100% parameter description coverage. The description adds value by explaining that productId can be obtained from the List Products endpoint, providing context beyond the schema's generic description ('The identifier of the Product').

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 tool returns a list of Segments for a given product, with a specific verb ('returns') and resource ('Segments'). It distinguishes from sibling tools like create-segment, delete-segment, update-segment, and get-segment by implying read-only listing behavior.

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 provides a prerequisite: the productId can be obtained from the List Products endpoint. This gives clear guidance on how to acquire a required parameter. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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