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

Annotations only declare destructiveHint=false; the description adds crucial behavior: this is a WRITE, returns the new record, uses POST /create, and is 'Not retried' — a meaningful idempotency warning that prevents duplicate creates. It stops short of describing permissions or error modes, but the key side effect is 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?

Front-loaded with 'WRITE: create one record', then necessary context in tight sentences. No filler; every clause (mandatory fields, return value, endpoint, no retry) earns its place.

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 create tool with nested dynamic fields and no output schema, the description covers the critical concerns: mandatory fields, where to find them, the return value, and the no-retry behavior. It omits error handling and permission requirements, but is otherwise sufficient to call correctly.

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 the baseline is 3, but the description adds actionable parameter guidance beyond the schema: all mandatory fields must be supplied, vtiger_describe_module lists them, and assigned_user_id usually comes from vtiger_get_me. This is real domain-level semantics for the nested fields object.

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?

Starts with 'WRITE: create one record in a module' — a specific verb, resource, and scope. Examples (lead, contact, account, deal, case) make the resource concrete and distinguish it from sibling read/update tools without needing to open schemas.

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?

Clearly tells the agent to send every mandatory field, points to vtiger_describe_module for the list, and explains assigned_user_id via vtiger_get_me. It does not explicitly say when not to use this instead of vtiger_update_record, but the 'create' framing makes the boundary clear.

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