SEO ROI Calculator

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the agent knows this is a side-effect-free local computation. The description adds the set of metrics produced, but says nothing about determinism, unit/currency assumptions, or how the break-even figure is derived. Adequate given annotation coverage, but not rich.

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?

A single front-loaded sentence with zero filler; the verb and the deliverable metrics come first. It is efficient, though the brevity is achieved by omitting information the agent actually needs rather than by tight editing.

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?

With 5 parameters, 0% schema description coverage, and no output schema, the description should carry the burden of explaining inputs and return shape. It lists only output metrics and omits parameter units, the percent-vs-fraction convention, and the default/meaning of 'months', leaving the agent to guess at call semantics.

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% across 5 parameters, so the description is the only place meaning could be added — and it adds none. It lists outputs, not inputs, and gives no units or interpretation for monthlyInvestment, monthlyVisitors, conversionRatePct (percent vs fraction), valuePerConversion, or months (only hinted at by 'over a period').

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?

States a specific verb (Estimate) and resource (SEO return), then enumerates the computed outputs: conversions, revenue, ROI %, cost per conversion, break-even. That clearly separates it from the CPC/CPM/CTR calculator siblings, though it never names or contrasts with them explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when a sibling calculator (e.g. cpc_calculator or ctr_calculator) would be the better pick. Usage is only inferable from the tool name and the output list.

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