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

Annotations already establish readOnly/openWorld/non-destructive behavior, so the description is not carrying that burden alone. It adds genuine context beyond annotations: the tool executes through Orbitx's seat, passes data back 'as it is,' and enforces a read-only refusal behavior.

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 core purpose is front-loaded and the trigger phrase is useful, but the description carries filler such as 'Orbitx's MCP server...' and a registry listing URL that do not help an agent invoke the tool. It is compact but not every sentence earns its place.

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 simple read-only list tool with two parameters and no output schema, the description supplies the trigger, the read-only constraint, and what the call returns (open VCs with join links). It is complete enough to select and call, though limit semantics and response shape are left to inference.

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 input schema documents authCode thoroughly, but the description adds no parameter meaning at all. With schema description coverage at only 50%, the description should compensate for the undocumented 'limit' parameter; it does not.

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 first clause names an exact verb ('List'), resource ('open LiveKit VCs'), and expected result ('with join links'), so the core function is unambiguous. It stops short of a full 5 because it never names the very similar sibling 'orbitx__orbitx_vc_link' or says how this tool differs from it beyond the trigger phrase.

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 a direct trigger: 'When the user says any open VC / send the link — call this,' which tells an agent when to invoke it. It also notes the read-only context ('anything that buys, sells or writes refuses'), but it does not explicitly define when to choose an alternative tool instead.

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