llmconveyors-mcp

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

With no annotations provided, the description carries full behavioral disclosure burden effectively. It specifies credit consumption range (30-500), rate limits (10 req/min), required scope (jobs:write), and the agent's phased execution model including pause/resume 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?

Despite density, the description is efficiently structured with zero waste: purpose statement, execution mode details, operational constraints (credits/rate limit), auth requirements, and prerequisite check. Every clause provides actionable information essential for invocation.

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 a complex 28-parameter agent-based tool, the description comprehensively covers invocation prerequisites, execution lifecycle (phased vs. standard), and operational constraints. Minor gap: does not describe immediate return values, though the polling workflow implies async behavior.

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 has 100% description coverage, establishing baseline of 3. The description adds valuable workflow context for 'autoSelectContacts' by linking it explicitly to the phased execution gate, enriching semantic understanding beyond the schema's technical definition.

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 tool 'generates a tailored CV, cover letter, and cold email for a job application' using specific verbs and resources. However, it does not explicitly distinguish from sibling tool 'job-hunter-generate-cv', which likely performs a subset of these functions, potentially causing selection ambiguity.

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 guidance on phased execution ('set autoSelectContacts=false to pause for contact selection'), names specific sibling tools for the polling workflow ('poll with agent-status, respond with agent-interact'), and mandates prerequisites ('Check balance with settings-usage-summary before running').

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