link_person_to_deal

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

Discloses mutation (replaces) and auto-backup, but omits other traits like permission requirements, constraints (e.g., person must exist), or notifications. With no annotations, description bears full burden, so additional details are 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?

Extremely concise (two sentences), front-loaded with the main action, and every sentence adds value.

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?

Covers core semantics and behaviors adequately for a simple tool, though could mention if person must exist or what is returned. Still largely complete given no output schema.

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?

Parameter names are self-explanatory (deal_id, person_id), but schema coverage is 0% and description adds no extra meaning beyond the action concept. Adequate for simple parameters but not compensatory.

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 clearly states the action (setting person_id), resource (deal), and key side effects (replaces previous, auto-backup). It distinguishes from siblings like 'attach_contact_to_deal' by specifying the replacement behavior.

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?

Implies usage for updating the linked person on a deal, but no explicit when-to-use or when-not-to-use, and no comparison to alternatives.

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