make_organization_customer

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

The description claims idempotency ('Idempotent - safe to call on organizations that are already customers'), but the annotation sets idempotentHint to false, creating a direct contradiction. Additionally, the destructiveHint is true, yet the description implies the operation is safe, further confusing the tool's behavioral profile.

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 extremely concise, consisting of two sentences that convey the core purpose, idempotency, and parameter usage. Every sentence adds value without redundancy.

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?

Despite the tool being simple with one parameter, the contradiction between description and annotations undermines completeness. The description does not address the destructive hint or reconcile the idempotency claim with the annotation, leaving the agent uncertain about the tool's true behavior.

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 description adds significant meaning beyond the schema. While the schema only describes 'identifier' as 'a string that will be trimmed', the description explains it can be an organization ID or exact name when unique, providing crucial usage context.

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 clearly states the action ('Apply the Customer mixin to an organization') and the resulting effect ('appears in the Huly Leads > Customers view'). It uses a specific verb ('Apply') and resource ('organization'), distinguishing it from sibling tools like create_organization or update_organization.

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 description provides clear context on when to use the tool (when making an organization appear in Leads > Customers) and notes idempotency, making it safe to call on existing customers. It also specifies the acceptable input formats (ID or unique name). However, it does not explicitly exclude scenarios or mention prerequisites like organization existence.

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