BBQ MCP Server

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

The description adds significant behavioral context beyond annotations: it explains credential handling ('credentials are not stored'), token expiration ('expires after 1 hour'), security practices (HTTPS transmission, environment variable recommendation), and legacy device support. While annotations provide structural hints (not read-only, idempotent), the description enriches understanding of the authentication lifecycle and security implications.

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 clear sections (purpose, important notes, args, returns, security, examples) and front-loads key information. Some redundancy exists between 'Args' and schema descriptions, but each sentence serves a purpose in clarifying authentication behavior and security.

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 an authentication tool with no output schema, the description provides comprehensive context: it explains the purpose, parameters, security model, token behavior, and even includes practical examples. Given the annotations cover idempotency and non-destructive nature, and the schema fully documents inputs, the description completes the picture by addressing real-world usage concerns.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal extra context in the 'Args' section (repeating schema info) and provides usage examples that illustrate parameter application. It doesn't add substantial semantic value beyond the schema, but maintains clarity without contradiction.

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 specific action ('Connect to ThermoWorks Cloud'), resource ('ThermoWorks account credentials'), and purpose ('access live temperature data from your connected ThermoWorks devices'). It distinguishes this authentication tool from sibling tools like thermoworks_get_devices or thermoworks_get_live_readings by focusing on establishing the connection rather than retrieving data.

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 clear context for when to use this tool ('to access live temperature data') and includes examples for specific scenarios (older Smoke Gateway devices). However, it doesn't explicitly state when NOT to use it or mention alternatives like using environment variables for authentication, though it hints at this in security notes.

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