llmconveyors-mcp

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

No annotations provided, so description carries full burden. Discloses safety profile ('Read-only, no side effects') and authorization requirements ('Requires scope: settings:read'). Mentions returned fields ('provider names and availability status') but could elaborate on return structure format since no output schema exists.

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?

Three sentences with zero waste: purpose statement, usage guidance, and behavioral notes. Front-loaded with main action, logical flow from what-it-does to when-to-use to safety warnings.

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?

Fully adequate for zero-parameter discovery tool. Compensates for missing output schema by describing return content ('names and availability status'). Covers authentication and safety requirements that annotations would typically provide.

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?

Zero parameters per input schema (empty object), establishing baseline 4. Description correctly implies no filtering or configuration parameters are needed for this list operation.

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?

Description uses specific verb 'List' with clear resource 'AI providers that support BYO API keys'. Explicitly references sibling tool 'byo-key-set' to establish workflow positioning, clearly distinguishing this discovery tool from the configuration siblings.

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?

Provides explicit when-to-use guidance: 'Use this to discover which providers can be configured with byo-key-set before setting up BYO keys.' Establishes prerequisite relationship with sibling tool, indicating this should be called first to validate provider availability.

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