llmconveyors-mcp

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

No annotations provided, but description carries weight well: discloses ephemeral nature ('Does not store'), return value ('Returns the converted resume object'), and auth requirements ('Requires scope: resume:write'). Minor gap: no error handling or validation behavior described.

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?

Six sentences with zero waste: purpose → usage context → output behavior → storage limitation + alternative → auth scope → sibling relationship. Front-loaded with the core conversion verb and well-organized.

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?

Strong coverage for a no-annotation, no-output-schema conversion tool: explains input source, output format, persistence behavior, auth needs, and tool relationships. Minor gap: could specify the JSON Resume structure or validation constraints, but 'converted resume object' suffices for basic completeness.

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% (data: RxResume data object), providing baseline 3. Description adds valuable semantic context by expanding RxResume to 'Reactive Resume (RxResume) format' and clarifying the data comes from resumes 'exported from the Reactive Resume application', enriching the parameter meaning beyond raw 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?

Excellent specificity: states the exact conversion (RxResume → JSON Resume format), identifies the resource (resume), and distinguishes from siblings by naming resume-export-rx for the reverse operation and master-resume-upsert for storage.

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 'Use this to import' when-to-use guidance, clear 'Does not store' exclusion with explicit alternative (master-resume-upsert), and direct sibling reference for reverse conversion ('use resume-export-rx').

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