llmconveyors-mcp

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

No annotations provided, so description carries full disclosure burden. Successfully states 'Read-only, no side effects' for safety profile and 'Requires scope: resume:read' for auth requirements. Minor gap: no mention of potential rate limits or pagination 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?

Three sentences, each earning its place: (1) core functionality, (2) usage timing with sibling references, (3) safety/auth properties. No redundancy or fluff.

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?

Complete for a simple listing tool: covers output content (IDs/names/descriptions), usage context, auth, and safety despite missing annotations. Minor gap: no output schema provided and description doesn't specify return format (array vs object).

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?

Zero parameters per schema. Baseline 4 applies as there are no parameters requiring semantic explanation. Schema is empty object, confirming no input needed.

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?

Clear specific verb 'List' with resource 'resume themes' and explicit output fields (IDs, names, descriptions). Distinguishes from siblings by referencing resume-render and resume-preview as tools to use after this discovery step.

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?

Excellent explicit guidance: 'before calling resume-render or resume-preview' and 'to let the user choose a theme.' Names specific sibling tools as alternatives for the rendering workflow, clarifying this is a prerequisite discovery step.

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