create_contact

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

States mutation (create) but lacks disclosure of side effects (e.g., portal access grants, notification implications), permissions, reversibility, or default behaviors for boolean flags. No annotations to compensate.

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?

Single sentence of 13 words, no wasted words, front-loaded with key action and resource.

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?

No output schema, no annotations, and complex tool with 10 parameters, boolean flags, and optional associations. Description fails to explain return value, validation rules (e.g., existing client check), or follow-up actions.

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 covers all 10 parameters with descriptions (100% coverage). Description adds only the optional client association, but no additional meaning beyond schema. Baseline 3 appropriate.

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?

Clearly states the verb 'create' and resource 'contact record', with optional client association. Distinguishes from sibling tools like 'create_client' (creates a client) and 'search_contacts' (search, not create).

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?

Implied usage for creating contacts, but no explicit guidelines on when to use vs alternatives, prerequisites (e.g., client must exist for association), or when not to use.

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