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

No annotations are provided, so the description carries the full behavioral burden. It does disclose meaningful traits: creation is pseudonymous (handle only, no personal info) and restricted to adults, with a hard separation from the children's surface. It does not cover permissions, duplicate/error behavior, or what the call returns.

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?

Two compact sentences with the core action front-loaded. The '[KEEP · internal]' tag is wasted tokens, but the rest is tight and earns its place.

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?

A 5-parameter creation tool with no annotations, no output schema, and 0% schema coverage needs more than two sentences. Missing parameter semantics (subject_id, title, description) and any notion of the result or failure modes leave an agent under-equipped to call it correctly.

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 0% across 5 parameters, so the description must compensate. It only alludes to 'topic' and 'handle' ('pseudonymous; a handle, no personal info'), leaving title, subject_id, and description entirely undocumented in both the schema and the description.

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: 'Open a study group around a topic.' An agent can distinguish this from group_join/group_get/groups_list since those operate on existing groups. The '[KEEP · internal]' prefix is meta-noise but doesn't obscure the purpose.

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?

Gives a scope constraint ('For grown believers') and a boundary ('the children's coach is a separate, never-joined surface'), which implies who should and shouldn't call it. However, it never says when to create a new group versus joining an existing one via group_join, nor any prerequisites for calling it.

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