post-crm-v3-properties-objtype-groups_groups

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

No annotations are provided, so the description carries the full burden. It only mentions 'REQUIRES body parameter' but does not disclose behavioral traits such as side effects, permission requirements, error behavior, or response details. For a mutating POST operation, this 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 brief, with two short sentences. It is front-loaded with the core purpose. The last two clauses ('REQUIRES body parameter' and 'Check the inputSchema') are slightly redundant but not verbose. Overall, it is appropriately concise.

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?

With no output schema, the description should hint at what the response contains (e.g., the created property group) but does not. It also lacks any mention of prerequisite conditions, such as needing an existing object type. For a simple create tool with 4 parameters, the description is minimally sufficient but not complete.

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. The description adds no extra meaning beyond the schema; it merely instructs to check the inputSchema. The schema itself provides descriptions for all parameters, including examples and usage notes.

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 clearly states 'Create a property group,' using a specific verb and resource. This distinguishes it from sibling tools like post-crm-v3-properties-objtype_objtype (which creates a property) and GET groups endpoints.

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?

The description provides a clear context for the tool ('Create a property group') and notes a key requirement (body parameter). However, it does not explicitly state when to use this tool versus alternatives, such as when to create a property instead of a group, or when to use batch creation. Usage is implied from the purpose and name.

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