assign_agent_to_contact

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

The description adds 'automatically' and 'rotación' but does not disclose destructive behavior beyond the annotation. It fails to explain what happens to previous assignments or if confirmation is needed.

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 two sentences, efficient and to the point. However, the second sentence is slightly redundant. No fluff, but could integrate the UUID info more smoothly.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate but lacks information on return values, error cases, or post-assignment state. Minimal for completeness.

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 0% schema coverage, the description only restates the parameter name 'contact_uuid' without adding meaning. It does not explain how to obtain the UUID or any constraints beyond the schema.

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 tool assigns an agent to a contact automatically, using the contact's UUID. It distinguishes from siblings like update_contact by specifying 'rotación automática de Wasapi'. However, it's not as precise as possible.

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 is provided on when to use this tool versus alternatives, such as when to assign manually or update contact details. No exclusions or prerequisites are mentioned.

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