Create A New Group

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it returns HTTP 201 and the created object, but fails to disclose other behavioral traits like side effects, permissions, or error conditions. Minimal addition beyond annotations.

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 concise at two sentences plus a list of required parameters and API info. Slight redundancy with 'Document Markup records' repeated, but overall well-structured and 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?

The description provides context about creating groups within layers for Document Markup and lists required parameters. However, it does not explain nested objects like settings, the purpose of optional parameters, or how this fits into the broader workflow. Adequate 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?

Input schema parameters all have descriptions (100% coverage). The description lists required parameters but adds no extra meaning beyond the schema, especially for optional fields like order_index, color, visibility, settings.

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 the tool creates a new group within a layer for Document Markup records, specifying required parameters and the API endpoint. However, it does not explicitly differentiate from sibling tools like create_a_single_group or create_group_and_move_markups, leaving some ambiguity.

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 no guidance on when to use this tool versus alternatives. It lists required parameters but does not mention prerequisites, context, or exclusions. Siblings include similar group creation tools, making this a gap.

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