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 fully covered. The description adds only the REST path, which is structural rather than behavioral; it says nothing about auth, error behavior (e.g., missing contact), or what a contact record contains.

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 no filler. There is minor redundancy between the 'one contact of a customer' fragment and the endpoint path, which both convey the same resource, but overall it is tight.

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 simple two-param read tool with full schema coverage and annotations, the essentials are present. However, with no output schema, the description never indicates what fields a contact returns, so an agent cannot anticipate the response shape from the definition alone.

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%, so both customer_id and contact_id are already documented with their meanings and constraints. The endpoint path mirrors the two parameters but adds no syntax, format, or sourcing guidance beyond what the schema provides, warranting the baseline 3.

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 names the resource (a single customer contact) and the backing endpoint, which combined with the verb in the name tells an agent this is a single-record fetch. The singular framing implicitly distinguishes it from the list_customer_contacts sibling, but the first sentence ('One contact of a customer') leans heavily on the tool name rather than adding independent detail.

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?

There is no statement of when to use this tool rather than fieldpulse_list_customer_contacts or fieldpulse_get_customer. The agent is left to infer from the singular/plural naming that this retrieves one record by id, with no explicit routing guidance.

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