llmconveyors-mcp

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

With no annotations provided, the description carries full behavioral disclosure burden. It successfully documents: side effects ('Creates a new share record'), return values ('Returns a slug and public URL'), security model ('anyone can view without authentication'), and authorization requirements ('Requires scope: sessions:read'). Minor gap on idempotency or error handling keeps this from a 5.

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 covering purpose, returns, side effects, auth requirements, temporal usage, and analytics follow-up. Every sentence conveys distinct information with no repetition of the tool name or schema contents. Well front-loaded with the primary action.

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?

Given no output schema exists, the description compensates by detailing return values (slug, URL) and access patterns. For a 2-parameter creation tool, it adequately covers prerequisites, authorization scope, side effects, and downstream tool integration.

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 description coverage is 100%, so baseline applies. The description does not explicitly elaborate on sessionId or generationId beyond the schema's 'Session ID' and 'Generation ID' definitions. It provides workflow context implying valid IDs are needed, but does not add semantic meaning to the parameters themselves.

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?

The description opens with a specific verb ('Create'), clear resource ('shareable public link'), and exact scope ('generation's artifacts' listing resume, cover letter, emails). It distinguishes itself from sibling tools by naming specific workflows (job-hunter-run, b2b-sales-run) and related analytics tools (share-slug-stats).

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: 'Use after running job-hunter-run or b2b-sales-run to share the output' establishes temporal dependencies, while 'Use share-slug-stats to track views' directs to the complementary tool. This clearly positions the tool within the workflow pipeline.

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