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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds value by promising a complete record ("all fields" incl. addresses, terms, price tier) rather than a summary, but says nothing about behavior for a missing/invalid id or auth requirements.

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 short sentences, front-loaded with the scope and field coverage; the trailing endpoint path is marginally useful for API mapping and costs little. No filler or repetition of the title.

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, the description reasonably compensates by enumerating the major field groups returned (addresses, contact, terms, price tier, custom fields). Combined with annotations covering safety, this is nearly complete for a simple single-record getter; only error behavior is unaddressed.

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 coverage is 100% and the id parameter already documents its source (from sosinventory_list_customers) plus positivity bound. The description's "by id" adds nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("One customer by id") and immediately scopes it as a single-record fetch, which implicitly distinguishes it from sosinventory_list_customers. It does not name the sibling explicitly, so it falls short of full differentiation.

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 "by id" and the parenthetical field list imply the use case (fetch full detail for a known customer), but there is no explicit when-to-use, when-not, or named alternative such as sosinventory_list_customers for discovery.

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