llmconveyors-mcp

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

Excellent disclosure given no annotations: specifies synchronous execution, 'Consumes credits' (cost), 'Rate limited: 10 req/min' (throttling), and 'Requires scope: jobs:write' (authorization). No gaps or contradictions.

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?

Highly efficient with zero waste: front-loaded purpose ('Generate a CV synchronously'), followed by differentiators, operational constraints, and parameter guidance. Every clause delivers distinct value.

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 for a simple single-param tool with no output schema: covers purpose, limitations, costs, rate limits, and auth. Minor gap: does not specify output format (PDF/text) or return structure, though implied by 'produces'.

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 ('Prompt for CV generation...'). Description repeats this information ('Pass a prompt describing...') without adding syntax examples, format constraints, or semantic nuances beyond the schema.

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 verb ('Generate') and resource ('CV') with clear scope ('synchronously'). Explicitly distinguishes from sibling 'job-hunter-run' by noting it runs 'without running the full Job Hunter pipeline' and produces 'only a CV, no cover letter or cold email'.

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 clear trade-offs ('Faster but produces only a CV') and implicitly indicates when to use this versus the full pipeline. However, it does not explicitly name the alternative tool ('job-hunter-run') despite strong contextual implication.

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