create_group

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: failure on duplicate names, optional placement of measurements, and the return of the group with its UUID. It could mention permissions or side effects, but the provided details are valuable.

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 a single, focused sentence that efficiently conveys the action, optional behavior, failure mode, and return value without unnecessary words.

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?

Given the tool's simplicity and the schema's thorough parameter coverage, the description is largely complete. It includes essential context (duplicate handling, return info), though it could benefit from a hint about when to use this tool over sibling group tools.

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 description coverage is 100%, so parameters are already well-documented. The description's mention of placing measurements is somewhat redundant and doesn't add meaning beyond the schema's details like the distinction between UUIDs and indices.

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 action ('Create a new measurement group'), the resource, and an optional behavior ('optionally placing measurements'). It also mentions the failure condition and return value, distinguishing it from siblings like update_group and add_measurements_to_group.

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 context is clear: this tool is for creating new groups. However, it does not explicitly mention alternatives or when not to use it (e.g., use update_group for existing groups), so it falls short of the highest bar.

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