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 meaningful behavior: consent-based (may require pre-consent), pseudonymous (no identity reveal), and idempotent (repeatable without duplicate side effects). This goes beyond a generic 'join' statement, though it doesn't explain failure modes like consent denial.

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, front-loaded sentence: 'Join a study group' followed by a compact parenthetical of key traits. Every word earns its place, with no filler or repetition, making it concise and well-structured.

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?

This is a state-changing tool with 3 parameters, no annotations, and no output schema. The description omits return values, failure behavior, and consent mechanics. For an operation that may be blocked by consent, the agent lacks essential context to handle errors or interpret results, making the description incomplete.

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 0% and the description provides no parameter meanings. The required 'id' can be inferred as group identifier from context, but 'handle' and 'subject_id' are entirely ambiguous. The description fails to compensate for the low schema coverage, leaving the agent without enough guidance to populate parameters correctly.

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 uses a specific verb 'join' with a clear resource 'study group', and the parenthetical adds distinct behavioral traits (consent-based, pseudonymous, idempotent). This clearly differentiates it from sibling tools like group_create, group_get, and groups_list.

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: use this to join an existing group, with 'consent-based' suggesting a prerequisite and 'idempotent' indicating safe retries. However, it does not explicitly state when not to use it or name alternative tools, so the guidance remains implied rather than explicit.

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