gorelo_list_client_locations

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It implies a read-only action with 'List', but says nothing about pagination, ordering, error behavior, permissions, or the shape of the returned locations. This is a significant transparency gap for a tool with no annotation support.

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, direct sentence front-loads the verb and object with no redundant words. It is appropriately sized and every word earns its place.

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 a simple one-parameter list tool with no output schema and no annotations, the description is under-specified. It lacks any mention of return value format, pagination or limits, and possible edge cases, so an agent would not know what response to expect.

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 only defines clientId as a required number with no description (0% coverage). The description adds 'for a given client', which clarifies that clientId identifies the client, but this mostly restates the parameter name and does not explain how to obtain or format clientId or what a 'location' is. The description barely compensates for the missing schema documentation.

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 a specific operation (List) and resource (locations) with an explicit scope (for a given client). This clearly distinguishes it from siblings like gorelo_list_clients or gorelo_get_client, since no other sibling targets locations.

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 no guidance on when to use this tool versus alternatives, such as gorelo_get_client or gorelo_list_clients. It implies a clientId is needed, but does not state when this tool should be preferred or when it should not be used.

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