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

Beyond the annotations, it discloses the refusal codes (workspace_not_yours, delegation_entity_mismatch) and that they are reported rather than retried, the fact that the joined organisation is recorded as UNVERIFIED in the mandate-serving corpus, and the staged dry-run/confirmation-token binding with its mismatch rejection. The mutation profile is well covered by destructiveHint=true, and the description adds the side effects and failure modes the annotation cannot express.

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?

Sentences are front-loaded and each carries a distinct rule — gating condition, required identity, refusal behavior, side effect, staging protocol. It is dense and slightly repetitive with the schema on the business-email and never-invent points, but nothing is filler.

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 an eight-parameter, multi-step, irreversible join with no output schema, the description covers everything an agent needs: preconditions, required human-supplied values, the two-phase confirmation flow, side effects, and non-retryable errors. No return-value explanation is needed since the dry run's payload is what the confirmation binds to.

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 100%, so the baseline is 3; the description goes slightly beyond it by framing the name/email/company trio as a person-binding requirement that must come from the user's own words and that the endpoint refuses to join without. It does not add format or validation detail for key, new_uuid, or request_id beyond what the schema already states.

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 workspace) and pins the lifecycle state precisely: it only applies after a manifest has been ACCEPTED and the handshake has completed. That implicitly separates it from publish_manifest and get_exchange_answer, but no sibling tool is named explicitly, so it falls short of full sibling differentiation.

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?

It gives an explicit gating condition ("Use this ONLY after a manifest has been ACCEPTED"), an exclusion ("It never takes over an existing workspace"), and an exact two-call procedure with dry_run=true first and the confirmation_token second. It also warns against retrying refusals and against inventing identity values, which is the kind of when-not guidance most tools omit.

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