rawCall

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

No annotations provided, so description carries full burden. It discloses it's a debug backdoor and direct pass-through, but does not explain side effects, authentication needs, or whether operations are destructive. Some behavioral info is given (allowed tools and prohibition), but not comprehensive.

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?

Two sentences, no wasted words. Front-loaded with purpose, then key restriction. Perfectly concise for the information conveyed.

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?

Given no output schema and nested parameters, the description is brief. It lists allowed tools but doesn't explain how to use rawCall with specific tools, error handling, or return values. As a debug backdoor, this might be acceptable, but for an agent it leaves gaps.

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 0% (no descriptions for parameters). The description implies 'tool' selects one of the listed tools and 'args' are its arguments, but doesn't explicitly explain the meaning or format. For a 2-parameter schema with nested object, more detail is needed.

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 it's a debug backdoor for directly calling specific original Luckin MCP tools. It lists the allowed tools (queryShopList, searchProductForMcp, etc.) and explicitly excludes createOrder. This distinguishes it from sibling tools like quickOrder and confirmOrder.

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?

Explicitly states when to use (for the listed tools) and when not to use (createOrder is forbidden, must use quickOrder → confirmOrder instead). Provides clear context for agent decision-making.

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