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 usefully adds that results include confirmed competitors, pages/recent changes, pending suggestions, and evidence, but it says nothing about how filtering behavior works across the many optional parameters or about pagination.

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?

It is a single front-loaded sentence with no filler, and the core resource and result composition come first. The parenthetical detail is dense but still serves the purpose.

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 covers return values, but the 19 undocumented optional parameters are a major gap for calling the tool correctly. The description gives no parameter-level context, leaving the agent unable to know which filters to set.

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 19 optional parameters, and the description does not mention or explain any parameter. The agent gets no guidance on what url, days, action, status, range_preset, activity_only, or the unrelated-seeming ad_account/ig_user_id/campaign_name fields do.

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?

It states a specific resource and scope: SEO competitors for a property, split into confirmed tracked competitors and pending suggestions with evidence. It is clear what the tool returns, though it does not explicitly distinguish itself from the sibling search_get_competitor_changes.

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 explicit guidance on when to call this versus alternatives such as search_get_competitor_changes or search_get_keyword_gap. The phrase 'for a property' implies context but does not tell the agent which situations select this tool.

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