customer_detections

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

No annotations are provided, and the description does not disclose behavior such as pagination limits, header requirements (e.g., customer_slug), or side effects. The word 'query' implies a read operation, but no behavioral details are given, leaving the agent without critical safety or operational context.

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 very short but broken into a fragment 'Detections · query customerDetections.' followed by a long truncated JSON example. It is not front-loaded with a clear action sentence, and the abridged example reduces its usability and clarity.

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 and no annotations, this complex query tool (nested filter, pagination) needs a robust description explaining return values and behavior. The description only offers variable names and a partial example, leaving the agent without enough information to correctly invoke and interpret the result.

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 descriptions merely restate GraphQL types ('String', 'Int'), which adds little value. The example variables in the description provide some concrete structure for the filter object, but it is truncated and leaves many fields unexplained, so it only partially compensates for the schema's lack of semantic detail.

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 a GraphQL query 'customerDetections' and mentions variables like 'after' and 'first', implying a paginated list. However, it lacks a clear verb like 'list' or 'fetch' and does not explicitly state what the tool returns, making its purpose somewhat vague.

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?

There is no guidance on when to use this tool versus alternatives such as the singular 'customer_detection' sibling. The description only lists variable names and provides an example, with no context about when this query is appropriate.

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