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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds minimal extra behavioral context, only that it returns join links. It doesn't mention pagination or default limit, but that's in the schema. The auth parameter description is extensive but not about the tool's behavior itself.

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 very concise: one sentence plus a usage trigger. It's front-loaded with the core function and clearly states when to use it. However, the authCode description is long and could distract, but that's in the schema, not the tool description, so the description itself is efficient.

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 read-only list tool with annotations covering safety, the description is mostly adequate. It states what it lists and when to use it. However, it lacks details on pagination, default behavior, or relationship to sibling tools like orbitx_vc_link, which could be important for an agent to choose correctly. The openWorldHint suggests it can return dynamic results, but this is not explained.

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 50%: the authCode parameter has extensive description, but the limit parameter is not described in the schema. The tool description doesn't explain the limit parameter's meaning (e.g., max number of VCs to return), so the agent gets no added value for that half of the parameters. With one parameter fully documented and one not, the description doesn't compensate.

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 clearly states the tool lists open LiveKit VCs with join links, which is a specific verb and resource. It distinguishes itself from sibling tools like orbitx_vc_link (likely for direct linking) by focusing on listing, but doesn't explicitly differentiate from that sibling.

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 provides explicit trigger conditions ('When the user says any open VC / send the link — call this'), which is strong guidance for when to use it. However, it doesn't mention when NOT to use it or alternatives (e.g., when to use orbitx_vc_link), so it's clear on the positive trigger but lacks exclusion criteria.

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