llmconveyors-mcp

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

With no annotations provided, the description carries full disclosure burden and explicitly states 'Read-only, no side effects' and 'Requires scope: sessions:read,' covering safety profile and authentication needs. It does not mention rate limits or caching behavior, leaving minor gaps.

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?

Three sentences efficiently cover distinct concerns: functionality (what is retrieved), usage timing (when to call), and operational constraints (read-only, scope). Every sentence adds unique value beyond the structured fields with no repetition.

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 the absence of an output schema, the description details return content ('available agent types, supported features, and default settings'). Combined with auth requirements and usage guidance, this fully covers the tool's simple surface area (zero parameters, no annotations).

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?

The input schema contains zero parameters, establishing a baseline score of 4. The description appropriately makes no mention of parameters since none exist, requiring no compensatory documentation.

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 'Get the default session configuration,' providing a specific verb and resource. It distinguishes from siblings like 'session-create' by explicitly stating this is used 'before creating sessions,' clearly marking the workflow boundary between initialization and creation.

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?

The phrase 'Use this to discover what agents and capabilities are available before creating sessions' provides clear temporal guidance on when to invoke the tool. While it implies the alternative workflow (creating sessions), it does not explicitly name 'session-create' as the next step, stopping short of a 5.

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