llmconveyors-mcp

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

No annotations provided, so description carries full burden. Discloses safety profile ('Read-only, no side effects') and auth requirements ('Requires scope: settings:read'). Lacks rate limit or error behavior details, but covers essential behavioral traits for a read operation.

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?

Highly structured and front-loaded: purpose → usage contexts → safety/auth → alternative reference. Every sentence earns its place with zero redundancy across four efficient sentences.

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?

Complete for a zero-parameter read tool. Compensates for absent output schema by documenting return fields. Auth scope and safety disclosures cover what would typically be in annotations. No gaps given tool complexity.

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 input parameters (baseline 4). Description compensates for missing output schema by enumerating returned fields (email, name, subscription plan, credit balance), helping the agent understand data availability despite empty input schema.

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?

Specific verb 'Get' + resource 'current user's profile' with explicit field enumeration (email, name, subscription plan, credit balance). Clearly distinguishes from siblings like settings-usage-summary (detailed breakdown) and settings-preferences-get (preferences vs profile data).

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: 'check available credits before running agents (job-hunter-run, b2b-sales-run)' and 'verify account identity'. Names specific alternative tool for different use case: 'For detailed usage breakdown, use settings-usage-summary instead'.

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