customers__get_loyalty_counters

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

Read-only nature is already covered by annotations; the description adds a concrete MCP-server rate limit (10 requests per 60 seconds) and advises caching, which is useful behavioral context beyond the annotations. It does not cover response behavior, but that is less critical given the read-only annotations.

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?

Three compact sentences with no fluff; the purpose is front-loaded, and the parameter/rate-limit notes are directly actionable. It could be slightly better structured but is efficient.

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 the nested request and no output schema, the description is usable but incomplete: it covers the main inputs and rate limit, but does not explain guestIds or the shape/interpretation of the returned counters.

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?

With schema description coverage at 0%, the description compensates partly by explaining the metrics and periods enums and telling users where to get organizationId. However, it omits guestIds and does not describe the request wrapper, leaving a clear gap.

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 identifies the resource as guest loyalty counters with order counts/sums by period, which is specific enough to distinguish from generic customer info tools. However, it is a noun phrase without an explicit verb and does not name sibling differentiators.

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?

It provides operational guidance—where to obtain organizationId and a throttling/caching recommendation—but it does not explicitly address when to prefer this tool over siblings or state exclusions.

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