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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes beyond that by disclosing an identity-binding rule: the returned record is tied to the bearer token and any supplied ID must be consistent with it — a genuine behavioral constraint an agent would otherwise miss.

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, zero filler, with the primary retrieval behavior front-loaded and the constraint second. Nothing is redundant with the schema or annotations.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What remains thin is error behavior on an ID/token mismatch and confirmation that the parameter may be omitted — minor gaps for a single-parameter read tool.

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 0%, so the schema only gives an anyOf string/integer nullable type with no meaning. The description compensates by explaining that customer_id must match the token identity, but it omits that the parameter is optional (default null) and what a non-matching value produces.

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 (Get) and resource (customer record) plus a scope qualifier: the record is linked to the current bearer token. That scope meaningfully separates it from siblings like get_contact and list_contacts, though it never names those alternatives explicitly.

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 constraint 'A supplied customer ID must match that token' implies the use case (retrieving your own customer record) but the description never says when to prefer this over get_contact, list_contacts, or get_current_user. Usage must be inferred from the token-scoping sentence.

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