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

The description adds meaningful behavioral context beyond the annotations: joining switches the active organization and best-effort emails other members. It also covers the destructive nature implicitly by emphasizing fresh confirmation and idempotency checks. This aligns with destructiveHint=true and readOnlyHint=false, with no contradiction.

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 front-loaded with the core purpose and uses labeled sections for prerequisites, canonicality, idempotency, and confirmation. However, confirmation is stated twice ('Ask the user to confirm first' and 'Confirmation boundary'), and the phrase 'plus every prerequisite stated above' is vague and adds little. The boilerplate sections make it longer than necessary.

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 destructive, state-changing join operation with no output schema, the description covers the key contextual needs: user confirmation, active-organization switching, email side effects, prerequisites, and retry/idempotency guidance. It does not detail failure modes or the exact output shape, but it tells the agent to trust actual_tool_output and context_engineering, which mitigates that 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?

The schema coverage is only 50%; the required joinCode parameter has no schema description, but the tool description clarifies it as an 'invite join code' and shows it maps to a company via the confirmation message. The optional _corply_context is already well-described in the schema. Still, joinCode lacks format, length, or validation details, so the description only partially compensates.

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 opens with a clear action and resource: 'Join an organization with an invite join code.' This distinguishes it from sibling tools like invite_cofounders and invite_member, which handle the opposite side of the invitation flow. The verb 'join' combined with 'invite join code' makes the tool's role unambiguous.

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 gives important invocation conditions, such as requiring user confirmation first and authenticated active organization access. However, it never explicitly explains when to choose this tool over alternatives or when not to use it. The usage context is implied by the purpose, but no exclusions or sibling comparisons are provided.

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