zernio_get_google_business_performance

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

No annotations are provided to indicate safety or side effects. The description implies a read operation ('Get') but does not disclose authentication needs, rate limits, data freshness, or any potential side effects. For a read tool with no annotations, the description provides minimal behavioral context.

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 description is a single, concise sentence that effectively communicates the tool's purpose without unnecessary words or redundancy.

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?

The description lists the metrics returned but does not describe the response structure, aggregation level, or date range behavior. Given the lack of an output schema, the description could provide more context about the output format to aid the 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?

All three parameters have descriptions in the input schema (100% coverage), so the schema already conveys meaning. The description does not add additional semantic information beyond what the schema provides.

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?

The description clearly states the tool retrieves Google Business Profile performance metrics and lists specific metrics (searches, views, direction requests, calls, website clicks), distinguishing it from sibling tools like zernio_get_gmb_location_details or zernio_get_google_business_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 is provided on when to use this tool versus alternatives, prerequisites like account connection, or situations where another tool might be more appropriate. The description is purely functional.

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