llmconveyors-mcp

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

No annotations provided, so description carries full burden. Excellently discloses: 'Read-only, no side effects', 'No auth required', and specific return values ('shared artifacts: resume, cover letter, emails'). Covers all critical behavioral traits an agent needs.

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 sentences, each with distinct purpose: (1) action/identifier, (2) return values/auth characteristics, (3) use case + safety notes. No redundancy, front-loaded with the essential operation.

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?

For a simple 1-parameter retrieval tool with no output schema, the description is complete. Compensates for missing annotations by disclosing side effects and auth requirements, and compensates for missing output schema by describing return content.

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 has 100% coverage with 'Public share slug' already documented. Description adds minimal additional semantics ('by its slug'), serving primarily to link the parameter to the action. 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?

Cites specific verb 'Retrieve' + resource 'publicly shared resource' and scopes it with 'by its slug'. Distinguishes from siblings like share-create and share-stats by focusing on retrieval of content vs. creation or analytics.

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 clear context with 'Use this to view what a share link contains' and explicitly notes 'No auth required (public endpoint)'. Lacks explicit contrast with authenticated alternatives (if any exist), but clearly signals the public/unauthenticated use case.

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