Attach a contact

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

No annotations are provided, and the description does not disclose whether the action is destructive, read-only, or has side effects. It lacks any behavioral traits beyond the name.

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 one sentence, but it wastes space on redundant info ('POST /crm/organizations/{organizationId}/contacts', 'Tags: Organizations', 'Body: application/json') without being informative. It is under-specified, not concise.

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 no annotations, no output schema, and a minimal description, the tool is severely incomplete. It fails to explain what happens on success, error conditions, or prerequisites like whether the contact must already exist.

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%, and the description does not explain any parameters. The schema indicates 'organizationId' and 'contactId' are needed, but the description adds no meaning or guidance on values.

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 gives the HTTP endpoint, but it fails to specify what the contact is being attached to. The path implies attaching to an organization, but this is not clarified. The sibling tool 'weeek_attach_a_contact' without _2 suggests duplication with no differentiation.

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 vs alternatives like 'weeek_attach_a_contact' or 'weeek_detach_a_contact'. No context on prerequisites or use cases.

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