POST /potentialCustomer (Potential Customer)

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

Annotations already indicate a write (readOnlyHint=false) and non-destructive operation. The description adds example fields but no behavioral traits beyond what annotations imply, such as side effects or authentication needs.

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 front-loaded with purpose but includes a large example block. It could be more concise while retaining utility. The Portuguese language may limit accessibility for English-speaking agents.

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?

Though an example is given, the description does not clarify which fields are required, what the response contains (no output schema), or error handling. For a creation tool, this leaves critical gaps.

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?

The single 'body' parameter is described as containing fields in the tool description. The detailed example JSON adds meaning beyond the generic schema object, showing many nested fields and their structure.

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?

Description states it registers a potential customer (CRM deal) in Conexa, which is a specific verb+resource. However, it does not distinguish from sibling tool create_customer, which likely does a similar function for regular 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?

No guidance on when to use this tool versus alternatives like create_customer. No when-not or prerequisite conditions. The description only provides an example body without contextual usage advice.

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