llmconveyors-mcp

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

With no annotations provided, the description carries full disclosure burden and succeeds in revealing critical security behavior: 'The key value is returned ONLY in this response and cannot be retrieved later, so save it immediately.' Also discloses authentication requirements. Minor gap: doesn't mention rate limiting or idempotency characteristics.

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 sentences with zero waste: purpose (sentence 1), critical security warning (sentence 2), auth prerequisite (sentence 3), and sibling navigation (sentence 4). Information is front-loaded logically with the most critical warning (one-time secret) prominently featured.

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?

Excellent coverage for a credential management tool with no annotations or output schema. Includes creation behavior, security disclosure, auth scope, and sibling mappings. Minor deduction: without output schema, could briefly characterize the full return object structure beyond just the 'key value'.

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 description coverage is 100% (all 4 parameters documented in schema), establishing baseline 3. The description mentions 'specified permission scopes' which aligns with the 'scopes' parameter, but doesn't add extensive semantic detail beyond what the schema already provides for label, expiresAt, or monthlyCreditsLimit.

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 states a clear specific action ('Create a new platform API key') with the resource type and differentiates from siblings by explicitly naming 'api-key-list' and 'api-key-revoke' as alternatives for viewing or deleting keys.

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 the prerequisite ('Requires scope: settings:write') and provides clear alternatives: 'Use api-key-list to see existing keys' and 'Use api-key-revoke to delete keys you no longer need,' creating clear boundaries for when to use this tool versus siblings.

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