crm_create_object

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't mention that this is a write/mutation operation, what permissions are required, whether it's idempotent, what happens on failure, or what the response contains. 'Create' implies mutation but lacks essential behavioral context.

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?

The description is extremely concise at just 4 words, with no wasted language. However, this conciseness comes at the cost of being under-specified for a tool with 3 parameters and complex schema.

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 mutation tool with 3 parameters (including nested objects), 0% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool does beyond the obvious, provide parameter guidance, or describe behavioral aspects.

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?

With 0% schema description coverage and 3 parameters (objectType, properties, associations), the description provides no information about any parameters. It doesn't explain what 'objectType' accepts, what 'properties' should contain, or what 'associations' are for. The schema has enums and nested objects that need explanation.

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?

The description 'Create a new CRM object' states the basic action but is tautological with the tool name 'crm_create_object'. It doesn't specify what types of objects can be created or distinguish this tool from its many sibling tools like crm_create_company, crm_create_contact, etc., which create specific object types.

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 guidance is provided on when to use this tool versus the many sibling tools that create specific object types (companies, contacts, leads) or batch creation tools. The description offers no context about appropriate use cases or alternatives.

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