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'). Could elaborate on pagination or empty result handling, but covers critical behavioral traits.

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 concise sentences: purpose definition, usage guidance with examples, and technical constraints. Front-loaded with core action. Zero redundancy despite covering multiple dimensions.

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?

Appropriate for low-complexity tool (0 params, simple list operation). Describes return content (consent records with purpose/status) despite lack of output schema. Scope requirement disclosure adds necessary 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?

Zero parameters per schema and context signals. Per rubric, 0 params = baseline 4. Description implicitly confirms no filtering parameters by stating 'List all' without caveats about input constraints.

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 verb (List), resource (privacy consent records), scope (current user), and return details (processing purpose and consent status). Distinguishes from siblings privacy-grant-consent and privacy-revoke-consent by emphasizing read-only listing versus modification.

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: 'check consent status before running tools that require specific consents' with concrete examples (ai-generation, contact-enrichment). Also clarifies prerequisite scope requirement (settings:read).

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