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 real value by listing the fields the payload contains and warning that no list endpoint exists, but it says nothing about not-found behavior or whether identifier is a name, code, or numeric ID.

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 terse sentences, front-loaded with what is returned, then the no-list caveat, then the endpoint path. The raw GET path is low-value for an agent but takes little space.

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 one required parameter, no output schema and full annotation coverage, the description is nearly sufficient: it enumerates returned fields in lieu of an output schema. The only real gap is identifier format/type, which matters because lookup failures would be silent.

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% for the single parameter, so the baseline is 3. The description's 'by its identifier (name, ...)' arguably muddies rather than clarifies whether the identifier is a name or an opaque key — it could be read as the identifier being the customer name.

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: fetch one customer by identifier, and parenthetically names the fields returned (name, addresses, phone, notes). It is distinguishable from sibling getters by resource, though it never contrasts with safefood360_update_customer, leaving the read-vs-write distinction to the annotation.

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 vendor offers no customer list' is a genuinely useful usage constraint — an agent knows it cannot enumerate customers and must already have an identifier. However, there is no explicit guidance on when to prefer this over safefood360_update_customer or what to do when the identifier is unknown.

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