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

The description reinforces the annotations by marking this as a WRITE and warning that it creates a new record every call, which clarifies the non-idempotent and duplicate-risk behavior. It adds useful context beyond the annotations, though it does not discuss permissions, side effects beyond creation, or response behavior.

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 short, front-loaded with the WRITE marker and core action, and every sentence adds practical value: identity requirement, duplicate caution, and endpoint. There is no wasted prose.

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 complex 28-parameter create tool with low schema description coverage and no output schema, the description covers the essential identity rule and duplicate warning but omits many optional field semantics and does not mention what the create operation returns. It is adequate for basic invocation but incomplete for fully informed use.

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?

With 28 parameters and only 25% schema description coverage, the description does important work by stating that first_name and/or last_name or a unique display_name are needed. However, it leaves most of the large parameter surface unexplained, including status/account_type semantics and many address/contact fields.

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 uses a specific verb and resource: create a customer, explicitly scoped to lead or account records. It also distinguishes the action from listing by directing duplicate checks to fieldpulse_list_customers.

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?

It gives clear usage guidance by saying to check fieldpulse_list_customers first to avoid duplicates. It does not explicitly say to use fieldpulse_update_customer when a matching customer already exists, so the alternative path is only implied.

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