zernio_get_google_business_keywords

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

No annotations provided, so description carries full burden. It indicates a read operation ('get'), but omits behavioral details like whether it requires authentication, data freshness, pagination, or any side effects.

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?

Extremely concise (one sentence) with no wasted words. However, it may be too terse, missing opportunities to add value without becoming verbose.

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?

With no output schema, the description should hint at the return value (e.g., list of keywords with metrics). It does not. Also lacks behavioral transparency and usage context, making it less complete for an agent.

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% (all three parameters described), so baseline is 3. The description adds no additional meaning beyond the schema; it simply restates the tool's purpose. No elaboration on date format or accountId value.

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?

Clearly states the tool retrieves search keywords for a Google Business Profile. The verb 'get' and resource 'keywords' are specific, and it distinguishes from sibling tools like 'zernio_get_gmb_reviews' or 'zernio_get_gmb_locations'. However, could be more precise about the scope (e.g., 'search keywords' vs. all keywords).

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 use this tool versus alternatives, such as other Google Business tools like 'zernio_get_google_business_performance'. No prerequisites or excluded scenarios are mentioned.

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