llmconveyors-mcp

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

With no annotations, description carries full burden. It discloses the return value ('Returns a URL'), authorization requirement ('Requires scope: resume:write'), and the dependency on resume-themes. Missing minor operational details like file expiration or caching behavior.

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 redundancy. Front-loaded with core function, followed by return value, use case, prerequisites/alternatives, and auth scope. Every sentence earns its place.

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?

Compensates well for missing output schema by explicitly stating the return type (download URL). Covers sibling relationships, auth scope, and distinguishes from related tools. Sufficient for a file-generation tool without annotations.

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 'JSON Resume format' and 'specified theme' which align with schema, but adds no additional constraints, validation rules, or format details beyond what the schema already provides.

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?

States specific action ('Render'), input resource ('JSON Resume object'), and output formats ('PDF or HTML file'). Distinct from sibling resume-preview by contrasting file generation versus inline preview.

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 directs users to resume-themes first for theme selection, and explicitly names resume-preview as the alternative for quick inline previews without file generation. Clear when-to-use ('produce a polished, formatted resume for sharing or printing').

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