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

Annotation Contradiction: readOnlyHint=false says the tool is not read-only, yet the description states 'Read-shaped tools only (anything that buys, sells or writes refuses)' while also claiming the MCP can post. This directly contradicts the annotations and confuses whether this tool performs or enables writes.

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 functional purpose is front-loaded, but a large portion of the description is boilerplate about the Orbitx server, 'a live seat on The Wall,' and a registry URL. These sentences do not earn their place for correct tool invocation, making the description cluttered for a single-parameter tool.

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?

There is no output schema, so the description should clarify return values; it only gives route names '/auth' and '/x' without saying how an agent should use them. The authCode is optional in the schema but the description says it is required after auth, and the posting contradiction leaves the tool's actual effect unclear.

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% and the authCode parameter is already described in the schema with source and usage context. The description does not add meaningful parameter-level semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 sentence names a specific action and resource: 'Connect the user's X account to OrbitX' and identifies the output (auth and tweet.write links). This makes the core purpose distinguishable from most sibling data-fetch tools. However, 'so this MCP can post' conflicts with the later claim that writes refuse, which muddies the intended behavior.

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 usage context is implied: call this when a user needs to link their X account to OrbitX. There is no explicit when-not-to-use guidance or mention of alternatives such as x_link_start, x_link_verify, or auth_connect, so an agent is left to infer routing.

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