Estimate reach, engagements, clicks, conversions and unit costs from creator campaign budget, creator count, average reach and engagement rates.
Estimate reach, engagements, conversions and unit costs for a creator campaign plan.
| Name | Required | Description | Default |
|---|---|---|---|
| creators | Yes | ||
| avg_reach | Yes | ||
| budget_eur | Yes | ||
| click_rate_pct | No | ||
| conversion_rate_pct | No | ||
| engagement_rate_pct | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Estimate' implies a non-mutating calculation, but the description does not state whether the tool is read-only, requires authentication, has side effects, or returns deterministic results. It lacks meaningful behavioral detail beyond the purpose.
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 front-loaded sentence with no wasted words. It is concise, though for a six-parameter calculator with no other documentation, it may be too sparse to be fully appropriately sized.
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 six parameters, zero schema descriptions, no annotations, and no output schema, the one-sentence description is not complete enough. It does not explain parameter meanings, defaults, return values, or calculation behavior, leaving significant gaps for an agent to call the tool correctly.
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 description coverage is 0%, so the description must compensate. It mentions output metrics like reach, engagements, and conversions, which loosely correspond to some parameters (avg_reach, engagement_rate_pct, conversion_rate_pct), but it does not explain the required inputs, defaults, units, or the role of click_rate_pct. Compensation is minimal.
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 states a specific verb ('Estimate') and lists the calculated outputs (reach, engagements, conversions, unit costs) for a creator campaign plan. It is clear what the tool does, though it does not differentiate itself from siblings like engagement_check or draft_brief.
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 gives a domain context ('for a creator campaign plan') but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.