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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so safety is covered. The description adds real value beyond that: the data source (Search Console ranking markers), the ranking criterion, and a quota constraint ('Uses one keyword lookup: one topic per call') that tells the agent calls are metered and topics cannot be batched.

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?

Five short sentences, each carrying a distinct fact: what it returns, how it ranks, the one-topic-per-call constraint, the topic fallback, and the save step. Purpose is front-loaded and nothing is repeated verbatim from the schema.

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?

There is no output schema, and the description compensates by naming every returned field and the ranking logic. It also covers the full workflow context (topic sourcing from get_profile, downstream save_keyword_opportunities), so an agent has everything needed to call it and act on results.

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 per-parameter descriptions are already handled and the baseline is 3. The description goes beyond it by explaining that results are ranked by what the site can win, which gives 'limit' the meaning of 'top N by winnability' rather than arbitrary truncation, and by clarifying that 'topic' is a single seed search, not a list.

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+resource ('Real Google searches containing a topic') and enumerates the returned fields: monthly searches, difficulty 0-100, buyer intent, and a winnability ranking. It also distinguishes itself from data-adjacent siblings by noting it marks searches already ranked in Search Console, so an agent can tell it apart from get_search_queries or get_competitor_gaps.

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?

Gives a clear prerequisite ('If the user didn't name a topic, pick one from the business (get_profile)') and a clear follow-up ('save the best ones to the Action Center with save_keyword_opportunities'), naming both sibling tools. It does not explicitly exclude alternatives such as get_search_queries, so the when-not-to-use side is only implied.

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