llmconveyors-mcp

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

With no annotations provided, description carries full burden and successfully discloses credit consumption, required auth scope ('sessions:write'), and return value structure ('company info, positioning, value propositions'). Lacks details on idempotency or caching but covers primary operational concerns.

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 dense sentences covering purpose, return values, workflow sequencing, and constraints/auth. No redundancy—every sentence provides unique value beyond the structured fields. Well front-loaded with the primary action.

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 2-parameter tool with no output schema and no annotations, description fully compensates by detailing return structure, consumption costs, authentication requirements, and sibling tool relationships. No gaps given the complexity level.

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 (baseline 3). Description adds critical cross-parameter constraint that at least one of the two optional parameters must be provided, which is business logic not captured in the schema structure. Could further clarify precedence if both are provided.

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?

Description opens with specific verb+object ('Research a company and create a sender profile') and explicitly distinguishes from sibling 'b2b-sales-run' by stating this should be used before that tool, clarifying the workflow sequencing.

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 explicit when-to-use guidance ('Use this before b2b-sales-run'), mentions resource consumption ('Consumes credits'), and documents input constraints ('At least one of companyWebsite or companyName must be provided') that prevent misuse.

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