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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavior beyond annotations by noting that contacts are masked and by listing the data returned, though it does not explain how include_pii changes masking.

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 a single front-loaded sentence with no wasted words. It places the core action first and then enumerates the key returned fields compactly.

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 read-only single-customer tool with no output schema, the description usefully lists the returned data and the masking behavior. However, with 0% schema coverage on four parameters and no explanation of include_pii or orders_limit semantics, an agent lacks enough information to invoke it confidently in all cases.

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 0%, so the description carries the burden of explaining four parameters, but it does not mention workspace, customer, orders_limit, or include_pii directly. It only hints at orders_limit through "recent orders" and include_pii through "contacts masked," leaving required parameters and limits undocumented.

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 states a specific verb and resource: "Read one store customer." It also enumerates the returned data (groups, lifetime value per currency, recent orders), and the singular "one" distinguishes this from the sibling customers_search 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?

Usage is implied by "Read one store customer," so an agent can infer this is for fetching a single existing customer. However, the description does not explicitly state when to use it versus customers_search, nor does it mention prerequisites or exclusions.

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