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

No annotations are provided, so the description carries the full disclosure burden. It explicitly discloses the visible side effect of creating a card on the customer board and notes that all fields are optional but at least one must be non-empty. It could add return-value or duplicate-handling details, but the key mutating behavior is clearly stated.

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 tightly worded sentences: the first states the action and target stage, the second gives the input rule and the side effect. No filler or repetition; essential information is front-loaded.

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 simple creation tool with seven optional string parameters, no annotations, and no output schema, the description covers the main needs: what will be created, where it appears, and the minimum input requirement. Minor gaps such as the exact return payload or duplicate policy are acceptable for this tool.

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%, so the description must compensate. It adds a global constraint (all fields optional, at least one non-empty), which is valuable, but it does not clarify ambiguous fields such as 'title' or acceptable formats. Parameter names like email, phone, first_name, and company_name are mostly self-explanatory.

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?

States the specific action 'Add a lead card to the New stage' and the resource, clearly distinguishing it from sibling tools like crm_update_lead, crm_move_lead, or delete_crm_lead. The title reinforces the manual-creation intent.

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?

Clear context: this is the tool for initially creating a lead card in the New stage, with a practical rule that at least one non-empty field is required. It does not explicitly name alternatives or when-not-to-use conditions, but the use case is evident relative to update/move/delete siblings.

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