llmconveyors-mcp

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

With no annotations, description carries full burden. Discloses mutation ('Modifies stored preferences'), return values ('returns the updated values'), and auth scope. Minor gap: unclear whether update is merge or replace semantics.

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?

Four well-structured sentences: purpose, behavioral traits, usage examples, prerequisites. Every sentence earns its place with zero redundancy. Front-loaded with core 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?

Excellent coverage given 100% schema coverage and no output schema. Compensates for missing output schema by documenting return behavior ('returns the updated values'). Acknowledges sibling relationship (settings-preferences-get) for complete workflow 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% (baseline 3). Description adds semantic value by specifying agentType is 'optionally' scoped and providing concrete examples of preference contents (themes, generation settings, notifications) beyond generic schema descriptions.

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 'Update' with resource 'current user's preferences'. Distinguishes from sibling settings-preferences-get by contrasting action (update vs get) and explicitly referencing the get tool as prerequisite.

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?

Provides explicit workflow guidance ('Use settings-preferences-get first'), use-case examples ('configure default themes, generation settings, or notification preferences'), and permission requirements ('Requires scope: settings:write').

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