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

Annotations only say it is a non-read-only, non-idempotent, non-destructive create. The description adds the crucial behavioral fact that creation is FREE (database only, no credits) — a claim annotations cannot express — plus the constraint that scheduled checks are the sole mechanism for data collection. This is exactly the 'beyond annotations' value the dimension rewards.

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 single paragraph is front-loaded with the action and return value, then routes to the follow-up tool, then discloses constraints. Dense but every sentence earns its place; four separate facts in four sentences with no filler.

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 an 11-parameter create tool with no output schema, the description supplies the return value (configId), the follow-up workflow, the uniqueness constraint, the scheduling semantics, and the cost — everything an agent needs to call it correctly and without surprise.

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 parameters (domain, devices, scheduleInterval, serpDepth, etc.) are already fully documented in the schema. The description confirms the shape (domain + market + devices + schedule) and clarifies 'manual' means no schedule, but adds no syntax or defaults beyond the schema. Baseline 3 per the high-coverage rule.

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?

Names a specific verb ('Creates') and resource ('rank tracker config') and enumerates the config contents (domain + market + devices + schedule). It also names the sibling it hands off to (add_rank_tracking_keywords) and the reader (get_rank_tracker), distinguishing it from other create_* tools.

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?

Explicitly states the next step (add keywords with add_rank_tracking_keywords), that positions come only from the schedule and are read via get_rank_tracker, and that nothing triggers an on-demand check. It also states the uniqueness constraint (one tracker per domain+market per project) and that repeats are a validation error, so an agent knows when not to call it.

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