llmconveyors-mcp

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

With no annotations, the description carries full burden and discloses key behaviors: it 'Returns the session object with its ID,' requires scope 'sessions:write,' and explains the domain model ('Sessions organize multiple generations into a logical workspace'). Minor gap: doesn't specify collision behavior if client-provided sessionId exists.

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?

Five sentences with zero waste: opens with core purpose, explains return value, clarifies domain concept, specifies prerequisite workflow tools, and states auth scope. Each sentence earns its place with no redundant or tautological language.

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?

Despite lacking annotations and output schema, the description adequately covers the essential contract: inputs (via schema), outputs ('Returns the session object'), side effects (creates grouping resource), and auth requirements. Mentions sibling runtime tools (job-hunter-run, b2b-sales-run) establishing ecosystem context.

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% (both sessionId and metadata fully described in schema), establishing baseline 3. The description adds minimal semantic value regarding parameters—mentioning 'with a specific sessionId' implies usage context but doesn't fully compensate for the lack of output schema or describe metadata semantics.

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 uses specific verb 'Create' with resource 'session' and clear scope 'for grouping agent runs and their artifacts.' It distinguishes from other session management siblings (delete, get, list) by defining the conceptual purpose as a grouping/workspace mechanism.

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?

Explicitly states when to use: 'Use this before running job-hunter-run or b2b-sales-run with a specific sessionId.' It also notes the prerequisite scope 'sessions:write,' providing clear prerequisites and workflow context.

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