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

There are no annotations, so the description carries the full burden of behavioral disclosure. It fails to mention what the tool returns (e.g., a paginated list), pagination behavior, or that it is a read-only operation. The description only explains the data model, not the tool's 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?

The description is concise (three sentences) and well-structured, front-loading the definition of Location Groups. Every sentence adds context about the hierarchy, though the tool's actual operation is left implicit. No waste, but could be tighter.

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?

This is a simple list tool with only two optional parameters and no output schema. The description provides rich domain context but omits what the response looks like and any direct statement of return type. For a tool to be correctly invoked, an agent needs to know it returns a list and how pagination works; this description doesn't cover that.

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% description coverage for both parameters (page and page_size), so the schema already explains them fully. The description adds no parameter-specific meaning. According to the baseline rule for high schema coverage, a score of 3 is appropriate.

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 tool name 'location_groups_list' clearly indicates a list operation, but the description never explicitly states 'lists location groups' or 'returns location groups'. Instead it provides background on what Location Groups are, which is helpful but leaves the actual function implied. This is clear from the name but not from the description, so it's a moderate purpose clarity.

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 gives no guidance on when to use this tool versus alternatives. It implies usage when you need location groups, but doesn't state any selection criteria, exclusions, or mention any alternative. Sibling tools are different domains, so no differentiation is provided.

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