customers

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

With no annotations, the description carries the full burden. It only says 'query', implying read-only, but does not disclose pagination behavior, return format, or any side effects. The example variables hint at filter structure but add no explicit 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?

The description is brief, with no fluff, but it is underspecified. The example variables are truncated, and the entire description fits in two short lines, which is concise but lacks substance. It is not front-loaded with the most critical information because there is almost nothing beyond the bare function.

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 query tool with six parameters, no output schema, and no annotations, the description is inadequate. It does not explain the return shape, how filtering works, or relationship to sibling tools like 'customer'. The complexity of the query operation is largely unexplained.

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 schema provides 100% coverage but only with GraphQL type descriptors. The description lists variable names and provides an example filter object, which adds some semantic meaning by showing the expected structure (e.g., accessGroups, roles, users). However, it does not explain individual parameters or their effects in 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 says 'query customers', which provides a verb and resource, but it's vague and essentially restates the tool name. It doesn't specify whether this returns a list, supports filtering, or distinguishes from the singular 'customer' sibling tool.

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 guidance is provided on when to use this tool versus alternatives like 'customer' (singular). There is no mention of use cases or exclusions, leaving the agent to infer from the name alone.

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