group_join

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

With no annotations, the description carries the full burden, and it does disclose three real behavioral traits: consent is required, identities are pseudonymous, and the operation is idempotent (so retries are safe). That is meaningful for a mutation, but it omits failure modes, permission requirements, and what happens when the caller is already a member.

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?

A single front-loaded sentence with no filler or redundancy. The bracketed internal-use tag is process metadata rather than agent-facing content, but it costs almost nothing.

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 mutation tool with no annotations, no output schema, and three completely undocumented parameters, this description is far too thin. An agent cannot determine the required `id` semantics, membership preconditions, or the result of joining an already-joined group.

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% for three parameters, so the description must compensate and largely does not. It never explains what the required `id` refers to, nor how `handle` differs from `subject_id`; "pseudonymous" only faintly gestures at handle/subject_id semantics.

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 ("Join a study group"), which is unambiguous on its own. However, it does nothing to differentiate itself from nearby siblings like group_create, group_get, group_contribute, or groups_list, so an agent gets no help choosing among the group_* family.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. The only contextual hint is the bracketed "[KEEP · internal]" marker, which signals internal tooling but does not tell an agent when this is the right call versus group_contribute or group_create.

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