query_customers

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

With no annotations, the description carries full responsibility. It implies a read-only operation through 'list and filter' and gives a purpose, but it does not disclose pagination behavior, return format, or access requirements. It is minimal and not misleading, but lacks rich behavioral 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?

Two concise sentences, front-loaded with the primary action ('List and filter Acumatica customers'), with no unnecessary words. It earns its place by adding a use case.

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?

For a straightforward list tool, the description is fairly complete: it covers the purpose and usage context. It does not explain return values, but no output schema exists and the parameter schema covers query mechanics. It could mention alternatives like get_customer, but that is not critical.

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 100%, so the parameters are fully documented with examples. The description adds a small hint about filtering by credit terms, which is not in schema examples, but it does not explain syntax or add substantial meaning beyond the schema.

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 it lists and filters Acumatica customers, using a specific verb and resource. It distinguishes itself from siblings like get_customer (single record) and query_* tools for other entities by focusing on customer list operations.

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 clear usage context: 'Use this to look up customers by name, class, status, or credit terms for analytics and reporting.' It does not explicitly mention alternatives or when not to use it, but the implied use case is well-defined.

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