llmconveyors-mcp

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

No annotations provided, so description carries full burden. Discloses critical behaviors: 'Read-only, no side effects' (safety), 'Requires scope: sessions:read' (auth), and 'Heavier' (performance characteristics). Missing only edge case handling or rate limit details.

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?

Four sentences, zero waste: (1) core action, (2) return contents, (3) use cases, (4) performance comparison + safety + auth. Front-loaded with essential action in first sentence. No redundancy with structured fields.

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?

No output schema exists, but description compensates by detailing return contents ('generated CVs, cover letters, emails, and conversation history'). Auth requirements and sibling differentiation included. Complete for a read operation of this complexity.

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 (single 'id' parameter with 'Session ID' description). Description mentions 'session' implying the target but adds no syntax/format details beyond schema. Baseline 3 appropriate when schema documentation is comprehensive.

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 ('Load') + resource ('session') + scope ('all its artifacts, logs, and generation details'). Explicitly distinguishes from sibling 'session-get' by stating it returns 'complete session state' versus implying a lighter operation.

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 when-to-use ('review full agent outputs or prepare artifacts for download') and when-not-to-use ('Heavier than session-get, so prefer session-get for lightweight lookups'). Names the specific alternative tool for comparison.

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