setup

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

Built upon annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds key behaviors: no authentication required, always succeeds, returns specific fields, and explains demo mode behavior. No contradictions.

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 well-structured with a clear purpose, context on demo mode, and a list of return fields. Every sentence adds value, and it is front-loaded with the main purpose.

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?

Without an output schema, the description includes the complete return object fields. It covers error behavior (none), authentication needs, and the demo mode vs. full mode scenario, making it fully self-contained for a setup guide.

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?

No parameters exist, so baseline is 4. The description does not add parameter info, but that's irrelevant here. Schema coverage is 100%.

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 starts with a clear verb+resource: 'Show the LemonCake MCP first-run setup guide.' It distinguishes itself from sibling tools by stating 'Call this tool FIRST,' making its unique purpose obvious.

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 advises when to use the tool: 'Call this tool FIRST to learn what is missing and how to obtain a permit.' It explains the context of demo mode and provides guidance on what to expect based on credential status.

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