Create a contact

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

Annotations are absent, so the description must carry the full burden. It only reveals that the tool creates a contact via a POST request. There is no mention of permissions, idempotency, error conditions, or what happens on duplicate names. Minimal behavioral context is provided.

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 sentence plus endpoint and tags) and to the point. However, it sacrifices necessary detail for conciseness. While not verbose, it could be more structured with additional context.

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 has a nested input schema, many parameters, no output schema, and no annotations, the description is severely incomplete. It lacks information about return values, field constraints, and behavioral details, making it insufficient for an agent to use correctly.

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 fails to explain any parameters. It only notes 'Body: application/json' without describing the body fields (firstName, lastName, emails, etc.). The agent must rely solely on the schema names, which is insufficient for correct invocation.

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 'Create a contact' and provides the POST endpoint, clearly indicating the action and resource. However, it does not differentiate from sibling creation tools like weeek_create_an_organization or weeek_create_a_deal, though the name and title already specify the resource.

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 such as weeek_attach_a_contact or weeek_update_a_contact. The description provides no context about prerequisites or typical use cases, leaving the agent to infer 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.