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

readOnlyHint=true already establishes the safety profile, and the description adds the underlying endpoint (GET /location), which helps an API-aware agent reason about behavior. It says nothing about pagination defaults, result volume, or sort order beyond what the schema declares.

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?

Two short sentences with the resource and returned fields front-loaded, no filler. The trailing 'ServiceTrade API: GET /location' is marginally useful for endpoint-aware agents rather than wasteful.

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?

With no output schema, the description does list the returned fields, which partially compensates. However, for a six-parameter paginated list tool it omits pagination behavior and total-count semantics, leaving gaps an agent would need to discover by calling it.

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?

Schema coverage is 100%, so all six filters (name, page, limit, status, companyId, updatedAfter) are already documented with types and defaults. The description adds no filtering semantics or combination behavior beyond the schema, which is the expected baseline here.

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?

States a specific verb and resource ('List customer service locations (sites)') and names the fields returned (address, company, status, tags), so the agent knows exactly what it gets. It does not distinguish itself from the sibling servicetrade_get_location, so it falls short of a 5.

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 explicit when-to-use guidance and no named alternative. The agent must infer that this is the bulk-retrieval counterpart to servicetrade_get_location, and nothing tells it whether pagination or filters are required for large result sets.

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