llmconveyors-mcp

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

No annotations provided, so description carries full burden. It successfully discloses 'Read-only, no side effects' and auth requirement ('Requires scope: settings:read'), but omits rate limits or error behaviors.

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 efficient sentences with zero waste. Purpose front-loaded in sentence 1, usage in sentence 2, behavioral traits in sentence 3, and sibling differentiation in sentence 4. Each 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; description compensates by listing returned fields (credits used, remaining balance, usage by category). Covers auth requirements and side effect profile. Sufficient for a zero-parameter read operation.

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?

Zero parameters per schema (baseline 4). Description appropriately focuses on return value semantics rather than inventing parameter documentation where none exist.

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?

Excellent specific verb ('Get') + resource ('aggregate summary of API usage and credit consumption') with clear scope differentiation from sibling tool settings-usage-logs (aggregate vs individual entries).

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 when-to-use guidance ('check credit balance before running agents or to monitor spending') and explicit alternative named ('For individual usage entries with timestamps, use settings-usage-logs instead').

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