llmconveyors-mcp

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

No annotations provided, so description carries full burden. It effectively discloses 'Read-only, no side effects' and auth scope requirement. Could enhance further by mentioning caching behavior or rate limits, but covers essential safety profile.

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 tightly constructed sentences with zero waste: sentence 1 covers purpose and filtering, sentence 2 describes return values, sentence 3 covers behavioral traits, scope, and sibling reference. Well front-loaded.

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 listing example return content ('default themes, generation settings'). Sibling relationship clarified. Minor gap: could specify return format (object vs array) for complete clarity.

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% (agentType fully documented), so baseline is 3. Description mentions 'optionally filtered by agent type' which aligns with schema but doesn't add semantic meaning beyond what the schema already provides.

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?

Description opens with specific verb 'Get' + resource 'current user's preferences' and explicitly distinguishes from sibling tool 'settings-preferences-update' by naming it as the alternative for modifications.

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 directs users to 'settings-preferences-update to modify preferences' establishing clear when-not-to-use boundaries, and notes the scope requirement 'settings:read' for prerequisites.

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