competlab-mcp-server

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

No annotations provided, so description carries full burden. It discloses 'Read-only' (safety trait) and return format ('Returns JSON object'), and adds context that the data structure mirrors get_positioning_dashboard. However, it omits details on error handling, performance characteristics, or side effects.

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?

Five compact sentences with zero waste. Front-loaded with core action, followed by structural context, use case, prerequisites, and safety—all earning their place. No redundant or filler text.

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 2-parameter historical lookup tool without output schema. Compensates for missing return schema by referencing get_positioning_dashboard's structure. Covers temporal scope, prerequisites, and read-only nature adequately.

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 coverage is 100%, establishing a baseline of 3. The description adds valuable semantic context by specifying that runId must come from get_positioning_history, helping the agent understand the dependency chain and data provenance.

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 uses a specific verb ('Get') and resource ('competitor-by-competitor Positioning data') with clear scope ('specific historical run'). It effectively distinguishes from siblings by contrasting with get_positioning_dashboard ('for a past point in time' vs current).

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 ('investigate how competitor messaging evolved between runs') and clear prerequisites ('Requires runId from get_positioning_history'). Lacks explicit 'when-not-to-use' or direct alternative naming (though it implies dashboard is for current data).

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