Get Atera customer

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

The readOnlyHint and idempotentHint annotations already disclose the main behavioral traits, and the description is consistent with them. It does not add extra behavioral context such as error behavior for an unknown customer ID, but with annotations present the minimal disclosure is acceptable.

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?

One short, front-loaded sentence with no filler. Every word contributes to identifying the action, the resource, and the parameter.

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 one-parameter, read-only, idempotent getter, the description is nearly complete. The absence of an output schema is partially offset by the simple nature of the operation, though a bit more detail on response or not-found behavior would make it fully complete.

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 0% schema description coverage, the description compensates by identifying the parameter as the numeric Atera customer ID. This is the only parameter and the description gives enough meaning for an agent to populate customerId correctly, although it does not add details about where the ID comes from.

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 uses a specific verb ('Get') and resource ('one customer') and adds the identifying scope ('by numeric Atera customer ID'). It clearly distinguishes this from atera_customers_list, which would retrieve multiple customers.

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 phrase 'one customer by numeric Atera customer ID' gives a clear usage context: use this tool when you have a specific numeric customer ID and need that single customer. It does not explicitly mention alternatives or when not to use it, but the singular-by-ID framing is sufficient for such a simple getter.

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