llmconveyors-mcp

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

With no annotations, description carries full burden and succeeds well: discloses security behavior ('stores securely'), authorization requirements ('Requires scope: settings:write'), and business logic implications ('unlimited AI generation but still pay for credits'). Minor gap: doesn't specify if operation is idempotent or overwrites existing keys.

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?

Four tightly constructed sentences with zero waste: action definition → business context → security/auth requirements → related tools. Front-loaded with verb and logically sequenced.

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?

Comprehensive given no annotations and no output schema. Covers security, billing, authorization, and sibling relationships. Would benefit from note on validation behavior or overwrite semantics, but adequately complete for safe invocation.

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%, establishing baseline 3. Description references provider example '(e.g. gemini)' which schema already covers, and does not add additional syntax details, constraints, or format guidance beyond the schema definitions.

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?

Specific verb 'Configure' with clear resource 'BYO API key'. Explicitly distinguishes from siblings by naming byo-key-get (check) and byo-key-remove (delete), clarifying this is the setter.

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?

Excellent explicit guidance: names prerequisite (settings-supported-providers), alternative action (byo-key-get to check), and destructive alternative (byo-key-remove). Provides clear workflow context.

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