Attach a contact

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention side effects, prerequisites, error handling, or whether the operation is reversible. The simple mention of 'POST' implies creation, but no further details are given.

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 very short (one line), but it includes the endpoint, verb, and tags. While concise, it sacrifices completeness. It could be more structured with bullet points, but given its brevity, it is not overly verbose.

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 tool with 2 parameters, nested objects, and no output schema, the description is insufficient. It does not explain the relationship between dealId and contactId, nor does it provide context about the operation. The agent would need to guess the inputs and 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?

Schema description coverage is 0%, so the description must compensate. It only says 'Body: application/json', which adds no meaning beyond the schema. The parameters dealId and contactId are not explained, leaving the agent without clarity on their purpose or format.

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 states 'Attach a contact' and provides the endpoint POST /crm/deals/{dealId}/contacts, making the action and resource clear. The 'Tags: Deals' further clarifies context. However, it does not explicitly state that it attaches a contact to a deal, relying on the endpoint structure.

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 sibling tools like weeek_attach_an_organization or weeek_attach_a_tag. The description lacks any when-to-use, when-not-to-use, or alternative suggestions, leaving the agent to infer usage from the name alone.

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