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

Goes beyond annotations by noting the group is created empty and cannot be deleted through this server, a meaningful lifecycle constraint on a non-idempotent write. It also explains the consequence of the public flag. It omits any note on response contents or failure modes.

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?

Three short sentences, front-loaded with a WRITE marker and the verb+resource, with no filler. Every clause carries information an agent can act on.

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 two-parameter create tool with no output schema, the description covers intent and constraints but says nothing about what comes back (e.g., the new group ID) that an agent would need for follow-up calls. Annotations cover the safety profile, so the gap is limited but real.

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 baseline is 3, but the description adds real meaning to is_public — public groups surface on subscription forms, private ones stay internal — beyond the schema's bare 'true = public group'.

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?

States a specific verb and resource ('create a new, empty group') and clarifies terminology by equating group with mailing list, which matters because a sibling is named create_mailing. It does not explicitly contrast itself with that sibling, so it stops short of a 5.

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 public/private explanation implies when each variant is appropriate, but there is no explicit guidance on when to create a group versus using create_mailing or add_member_to_groups. Usage must be inferred.

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