Compute the absolute and percentage difference between two traffic values to detect traffic changes for SEO analysis.
primitive: Calculate the delta between two traffic metrics (absolute and percentage).
| Name | Required | Description | Default |
|---|---|---|---|
| current | Yes | Current value | |
| previous | Yes | Previous value | |
| engine | No | The search engine (optional) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description labels the tool as 'primitive,' implying a straightforward computation with no side effects. However, there are no annotations to confirm this, and the description does not explicitly state that the operation is safe or read-only. The behavioral disclosure is minimal but not misleading.
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 very short—a single sentence—and gets the point across without unnecessary detail. It is front-loaded and efficient, though it could be slightly more structured.
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 that there is no output schema, the description would benefit from specifying the output format (e.g., returns object with absolute and percentage delta). As is, it is adequate for a simple calculation but lacks details an agent might need to use the result.
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%, so the parameters are already well-documented. The description does not add extra meaning beyond what is in the schema. It mentions 'absolute and percentage' in the output context, but does not clarify how parameters relate to this.
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 it calculates the delta between two traffic metrics, including absolute and percentage values. However, it does not specify what 'traffic metrics' means, leaving some ambiguity as to the exact input types. The 'primitive' prefix suggests it is a building block, but this is not explicitly differentiated from sibling primitives like seo_primitive_ranking_bucket.
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?
No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it. The description only states what it does, without providing any situational advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.