waha_set_group_subject

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action, but does not mention side effects, permission requirements, reversibility, or error behavior. This is a significant gap for a mutation tool, leaving the agent without crucial information about what to expect when invoking it.

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, short sentence with no filler words, making it highly concise and front-loaded. However, it is slightly too terse, omitting any contextual details that could be included without bloating it. Still, it is appropriately sized for a simple setter tool.

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 tool is a simple mutation with two parameters and no output schema, but the description is far from complete. It does not explain what happens on success (e.g., success message, updated group object), failure modes, or whether the group must exist. Combined with absent annotations and partial parameter descriptions, this leaves the agent without sufficient context to fully understand the tool's consequences.

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 50%: only the 'subject' parameter has a description. The description repeats 'subject' without adding detail, and it does nothing to clarify the meaning of 'groupId' or the expected format/behavior of the parameters. The description adds marginal value beyond the schema, failing to compensate for the missing parameter 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 'Set the group name/subject' clearly states the action (set) and the resource (group name/subject), distinguishing it from sibling tools like waha_set_group_description and waha_create_group. It is specific and unambiguous about the tool's core 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 implies usage when you want to rename a group's subject, but it provides no explicit context about when to choose this tool over alternatives, nor does it mention any prerequisites such as group existence or required permissions. It is not misleading, but offers no exclusionary guidance.

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