llmconveyors-mcp

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

With no annotations, description carries full burden. Discloses 'Does not modify the resume' (safety) and 'Requires scope: resume:write' (auth), which are essential. Mentions 'returning any errors and warnings' but lacks output structure details, rate limits, or success/failure behavior expected when no output schema exists.

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?

Three tightly constructed sentences: functional description (what it does and returns), usage guidance (when to invoke), and operational constraints (non-destructive, auth scope). Every sentence earns its place with zero redundancy.

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?

Appropriate for a single-parameter validation tool. Covers workflow position, safety guarantees, and authorization requirements. Lacks detailed output schema description (no output schema provided), but 'returning any errors and warnings' provides sufficient conceptual coverage for a validation utility.

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% (single 'resume' parameter fully documented). Description adds semantic value by explaining what validation entails: 'missing fields, invalid formats, incomplete sections', enriching understanding of the parameter's purpose beyond the schema's 'Resume object in JSON Resume format'.

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 (Validate) and resource (resume object) with clear scope (JSON Resume schema). Distinguishes from siblings by positioning in workflow 'after parsing or editing' and 'before rendering or submitting to agents', clearly differentiating from resume-parse and resume-render functions.

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?

Explicit temporal guidance: 'Use this after parsing or editing... before rendering or submitting'. Provides clear workflow sequencing that implicitly defines when to use vs alternatives. Lacks explicit naming of sibling alternatives (e.g., 'use resume-parse for unstructured data').

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