get_customers

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the module requirement and basic purpose. It does not describe whether the tool is read-only, what the output format is (array of objects?), or any side effects of parameters like filters. Given the lack of annotations, this is insufficient.

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 with two sentences. The first sentence states the purpose, and the second provides a usage condition. No redundant information is present, though it could be more structured.

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 8 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain return values, pagination, or how filtering parameters work. The description does not adequately equip an agent to use the tool correctly without additional context.

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 description coverage is only 13% (1 out of 8 parameters have descriptions). The tool description adds no parameter information beyond the schema, failing to compensate for the low coverage. For example, 'limit' has no description, and the meaning of filters like 'created_at_from' is unclear.

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 retrieves customers (repeat clients/subscriptions) and requires the Customers module to be enabled. While it distinguishes from sibling tools by being the only customer-related endpoint, it lacks an explicit verb like 'get' or 'list', though it is implied.

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 ('Use if the Customers module is enabled') but offers no guidance on when to use this tool versus alternatives, nor does it mention scenarios where it should not be used. The sibling tools cover other entities, but no direct alternative for customers is given.

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