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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the taxonomy of change types, but says nothing about defaults when days/date_from/date_to are omitted, how results are ordered or capped, or why ad/IG/campaign parameters exist on a competitor-page tool.

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 no filler, and the change types are listed where an agent will see them first. Its brevity is efficient, though it borders on under-specification for a 19-parameter tool.

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?

An output schema exists, so return shape needn't be explained, but with 19 optional parameters at 0% coverage and no usage context, the definition is far too thin for the tool's complexity. Key ambiguities an agent must resolve before calling are left unaddressed.

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?

All 19 parameters have 0% schema description coverage and the description mentions none of them. It doesn't clarify the overlapping filters (url vs site_url, days vs date_from/date_to/range_preset, action vs status) or the seemingly unrelated ones (ad_account, ig_user_id, campaign_name, property_name), leaving an agent to guess.

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 resource (recent changes on tracked competitor websites) and enumerates the change types returned (new pages, removed pages, changed titles/H1s). It is clearly distinguishable from analytics siblings, though it never contrasts itself with the closest sibling, search_get_competitors.

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 on when to call this versus search_get_competitors or search_get_page_metadata, and no prerequisites (e.g. whether a competitor must already be tracked). The only usage signal is implicit in the name.

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