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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, so the agent knows it mutates membership. The description adds nothing beyond that: it does not say what joining entails (membership granted, notification to team, effect on progress), what happens with an invalid or expired code, or whether joining is reversible.

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 opening sentence is well front-loaded and earns its place. The two trailing negative sentences are off-topic boilerplate unrelated to team joining and dilute the guidance rather than sharpen it.

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 tool with full schema coverage and annotations, the definition supplies the essential trigger and input expectation, so an agent could call it correctly. It is still thin on outcome and error behavior for a membership-changing action, which is the main remaining gap.

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 100%, so both parameters are already documented, including the tap token's origin from keep_progress and the code's ability to accept a full link. The description's phrase 'invite code or link' merely echoes the schema and adds no format, validation, or failure 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?

The description states a specific verb and resource ('join' a '2hives team') and ties it to the triggering input ('invite code or link'), so the agent can recognize the intent without opening the schema. It stops short of naming the adjacent tools (join_challenge, join_live_group, create_team) that an agent might confuse it with.

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 a clear positive trigger: the user has an invite code or link and wants to join a team. However, the stated exclusions ('Not for medical questions, emergencies or a crisis. Not for general chat about meditation') are generic scope disclaimers rather than routing guidance, and the definition never points to join_challenge, join_live_group, or create_team as the alternative when the user lacks a code.

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