llmconveyors-mcp

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

Annotations are absent, so description carries full burden. It successfully discloses 'Read-only, no side effects' and authentication requirement ('Requires scope: settings:read'). Mentions pagination behavior. Could add details on rate limits or error conditions, but solid coverage for a read tool.

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: 1) resource definition, 2) use case guidance, 3) safety/auth constraints, 4) sibling distinction. Front-loaded with most critical info. No redundancy.

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 partially compensates by listing fields in entries (action type, credits, timestamps). Covers auth scope and pagination. For a simple 2-parameter read tool, adequately complete without excessive verbosity.

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% (both offset and limit are documented in the schema). Description mentions 'paginated' providing context for why these parameters exist, but doesn't add syntax details beyond schema. Baseline 3 appropriate when schema does heavy lifting.

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 specificity: states exact verb (Get), resource (usage logs), and data fields returned (action type, credits consumed, timestamps). Explicitly distinguishes from sibling tool 'settings-usage-summary' by contrasting individual entries vs aggregate overview.

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 states when to use ('audit specific credit charges or investigate unexpected usage') and explicitly names the alternative tool for different use case ('For an aggregate overview, use settings-usage-summary instead'). Clear boundaries established.

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