Leadpipe MCP

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds that it 'returns matched intent topics', hinting at output behavior, but doesn't disclose details like rate limits, authentication needs, or processing time. Since annotations cover safety, the description provides minimal extra context, meeting the lower bar but not enriching behavioral understanding significantly.

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?

The description is a single, efficient sentence with zero waste: 'Analyze a website URL and return matched intent topics.' It front-loads the core action and outcome, making it easy to parse. Every word contributes to understanding the tool's function.

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?

Given the tool's moderate complexity (analyzing websites for topics), annotations cover safety, but there's no output schema. The description mentions the return value ('matched intent topics'), but doesn't explain format, structure, or potential errors. It's adequate for a read-only tool but lacks depth for full contextual understanding.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It specifies 'website URL', clarifying the 'url' parameter's purpose beyond the schema's format constraint. However, it doesn't detail URL requirements (e.g., valid protocols, depth limits). With only one parameter, this is sufficient for a high baseline.

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?

The description clearly states the tool's purpose: 'Analyze a website URL and return matched intent topics.' It specifies the verb ('analyze'), resource ('website URL'), and outcome ('return matched intent topics'), making the function unambiguous. However, it doesn't differentiate from sibling tools like 'search_topics' or 'list_topics', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, constraints, or compare it to siblings like 'search_topics' or 'get_topic_facets'. Without any usage context, the agent must infer applicability from the tool name alone.

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