Add a CRM contact

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

Annotations are all false so the description carries burden. It notes contact ids are unique within company, which is useful. However, lacks details on side effects, permissions, or return behavior.

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?

Two short, precise sentences with no waste. Front-loads the primary purpose and adds a key constraint (unique id).

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?

Missing important context: no return value description (no output schema), no explanation of the required 'project' parameter, no error conditions (e.g., duplicate id behavior). For a creation tool, more guidance is needed.

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 low (17%); description lists fields (name, email, role, phone) but provides no syntax or validation rules. Does not explain 'project' parameter which is required. Adds moderate value beyond schema.

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 identifies the verb (add), resource (contact), and specifies fields (name, email, role, phone) and target (company). Differentiates from siblings like update_contact or remove_contact.

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 explicit guidance on when to use this tool vs alternatives. Implicitly for creating a new contact, but no exclusions or context about prerequisites or preferred use cases.

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