Unlock full timeline & evidence

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds critical context that credits are spent, the unlock is permanent and idempotent, and the website's verdict remains unchanged. This goes well beyond annotation coverage and prevents costly agent mistakes.

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?

Four dense sentences front-load the core effect, then cover cost, permission, idempotency, and behavioral context. Every sentence earns its place; there is no fluff or redundant restating of the title.

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?

For a single-parameter, cost-incurring mutation with no output schema, the description fully covers preconditions, side effects, pricing source, repeated-call behavior, and role boundaries. Nothing important is missing.

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 schema already provides complete documentation for the single required slug parameter ('Report slug'), so the baseline is 3. The description references read_report for cost info but does not add meaningfully new details about the slug parameter itself.

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 names a specific action ('permanently unlock') and a specific resource ('report's full timeline, evidence and SEO detail'), clearly distinguishing it from read-only tools like read_report. The scope is concrete: it affects a single account and is billing-relevant.

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 explicitly instructs the agent to quote the exact price from read_report's timelineLocked.cost field and call the tool ONLY after the user explicitly agrees to spend. It also clarifies there is no double-charge for already-unlocked reports, which is a clear precondition/exception guide.

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