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

The annotations already declare this is not read-only, is not idempotent, and is destructive; the description adds meaningful context that it records a request requiring owner approval before access is active. It also discloses security-relevant behavior: the URL is validated as a first-party session invitation rather than fetched as an arbitrary web page, and it returns refreshed connection/session state.

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, then covers the approval side effect, URL validation, return state, and the relevant alternative in a tight sequence. Every sentence contributes useful information without repetition.

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 one-parameter mutation tool with no output schema, the description covers the key prerequisites (verified account), the approval workflow, URL validation behavior, returned state, and the relevant alternative tool. An agent has enough information to select and invoke it correctly.

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 sole invite_url parameter is already documented. The description adds semantic constraint beyond the schema by explaining that the URL must be an existing Blender Bridge shared-session invitation and is validated as a first-party session invitation, not treated as an arbitrary web page.

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 action: joining a shared-computer invitation from a Blender Bridge invite_url and recording a request pending owner approval. It clearly distinguishes this from invite_collaborator and identifies the app-only nature of the adapter.

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 clearly establishes the use case as joining an existing shared-computer invitation and explicitly names invite_collaborator for creating a new invitation instead. However, it does not explicitly distinguish this request step from accept_collaboration or decline_collaboration when the owner later responds.

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