llmconveyors-mcp

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

No annotations provided, so description carries full burden. Discloses 'Read-only, no side effects' (safety), 'Requires scope: sessions:read' (auth), return structure ('session objects with IDs...'), and pagination behavior ('paginated envelope with cursor for next page'). Rich behavioral context.

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?

Seven sentences with zero waste. Front-loaded with core action ('List sessions...'), followed by return format, usage context, pagination mechanics, safety/auth requirements, and alternatives. Every sentence earns its place.

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 the return structure (session objects with IDs/metadata) and pagination envelope. Covers auth scope and side effects. Complete for a 2-parameter read-only list tool.

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 (baseline 3). Description adds value by explaining the interaction: cursor is for 'cursor-based pagination' and when limit is provided, the tool returns a 'paginated envelope' rather than a simple list. This adds behavioral semantics beyond the schema definitions.

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) + resource (sessions) + mechanism (cursor-based pagination). Explicitly distinguishes from siblings session-get and session-hydrate by stating they provide 'full details for a specific session' while this tool is for browsing/resuming.

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 'Use this to browse existing sessions or find a session to resume' defines when to use. Named alternatives 'Use session-get or session-hydrate' for specific session details provide clear when-not-to-use guidance.

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