add_measurements_to_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 a key behavioral trait: 'Returns the UUIDs of the measurements added.' It also states the group must already exist ('existing group'). However, it does not disclose side effects such as whether duplicates are allowed or if the operation replaces existing memberships, which is notable for a mutation tool.

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: two sentences, front-loaded with the action, and no filler. Every word adds value—purpose in the first sentence, return behavior in the second.

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 simple tool with fully documented parameters, the description covers the essential aspects: action, target (existing group), and return value. It lacks details on edge cases or errors, but given the tool's simplicity and the schema richness, it is sufficiently complete. The absence of an output schema is mitigated by the explicit mention of return UUIDs.

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 the schema already documents both parameters thoroughly, including the group UUID source and the measurement UUID/index choices. The description does not add meaningful parameter semantics beyond the schema; it only restates 'one or more measurements' which mirrors minItems. Baseline 3 is appropriate.

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 is specific and clear: 'Place one or more measurements in an existing group' uses a direct verb and resource, distinguishing it from sibling tools that create, delete, or retrieve groups/measurements. It also states the return value, further clarifying its function.

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 clearly implies when to use the tool: when you need to add measurements to an existing group. While it doesn't explicitly mention alternatives, the context is unambiguous and the phrase 'existing group' signals a prerequisite. It lacks an explicit exclusions list but provides clear context.

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