llmconveyors-mcp

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

Compensates for absent annotations by disclosing return encoding (base64 for binary, plain text), safety profile ('Read-only, no side effects'), and auth requirements ('Requires scope: sessions:read'). Missing only error behavior 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 well-structured sentences cover: operation/return format, use case, prerequisite/auth/safety, and alternative tool. Information is front-loaded with no redundant phrases.

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 download tool: explains return encoding (compensating for missing output schema), documents auth scope, states prerequisites, and provides sibling differentiation. No gaps given the 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% coverage establishing baseline 3. Description adds workflow context explaining that 'key' comes from session hydration and the relationship between parameters and the prerequisite session-hydrate call.

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?

Specifies exact operation (Download), resource (artifact from session), and mechanism (by storage key). Explicitly distinguishes from sibling document-download by contrasting 'session context' vs 'storage path', and references session-hydrate as the key source.

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 explicit workflow prerequisite ('Get artifact keys from session-hydrate first'), concrete use cases ('rendered PDF resume or cover letter'), and clear alternative selection guidance ('For downloading by storage path... use document-download').

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