Create or Update RD Station CRM Contact

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation and idempotency are covered structurally. The description adds value by explaining the upsert semantics (match by exact email before creating) and that it returns the contact id. It could go further by noting whether existing fields are overwritten or merged, but the core behavioral traits are well disclosed.

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 compact, front-loaded with the core upsert behavior in the first sentence, and every sentence earns its place. The usage-example phrases are brief and concrete. No filler or 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?

For a 5-param flat tool with 100% schema coverage, required fields stated, idempotency and non-destructiveness declared via annotations, and no output schema expected (though it mentions returning contact id), the description is largely complete. It might benefit from noting partial-update semantics regarding omitted optional fields, but overall it's sufficient for effective agent invocation.

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 coverage is 100%, so all 5 parameters are described in the schema. The description adds useful supplementary semantics by clarifying that email is the matching key for upsert behavior, and that phone/title/notes are the optional fields being updated. It reinforces the required email+name constraint. A small gap: it doesn't clarify how the update interacts with omitted optional fields (whether they're preserved or cleared).

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 verb (create or update), resource (RD Station CRM contact), and the matching criteria (exact email). It distinguishes itself from siblings like rdcrm_search_contacts and rdcrm_get_contact by being the mutation/upsert tool, and explicitly mentions it returns the contact id.

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 when-to-use guidance with concrete examples ("add João to the CRM", "update Maria's phone"). It also explicitly states requirements (at least email and name) and notes which fields are optional, giving the agent a clear decision framework for invoking this tool.

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