crm_create_company_property

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 provides none. It doesn't mention whether this is a write operation requiring specific permissions, what happens on success/failure, whether properties are editable after creation, or any rate limits. For a creation tool with 11 parameters, this lack of behavioral context is a significant gap.

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 - a single 4-word phrase. While this is efficient, it's arguably under-specified rather than appropriately concise. However, it's front-loaded with the core action and doesn't contain any redundant information.

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 complex creation tool with 11 parameters, 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what a company property is, what the parameters mean, what the tool returns, or any behavioral characteristics. This leaves the agent with insufficient information to use the tool effectively.

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 11 parameters (5 required), the description provides no information about any parameters. It doesn't explain what 'name', 'label', 'type', 'fieldType', 'groupName' mean in this context, nor does it mention the 6 optional parameters. The description fails to compensate for the complete lack of schema documentation.

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 company property' restates the tool name with minimal elaboration. While it specifies the verb 'create' and resource 'company property', it doesn't distinguish this from sibling tools like crm_create_contact_property or crm_create_lead_property, nor does it explain what a 'company property' actually is in this CRM context.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or compare it to similar sibling tools like crm_create_contact_property or crm_create_lead_property. There's no indication of when this tool would be preferred over other property creation tools.

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