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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered elsewhere. Beyond that, the description adds no behavioral context: no note on what the audit returns, how long it takes, whether data is fetched live, or how the scraped dataset is validated.

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 duplicated verbatim and both copies cut off with ellipses, so an agent receives the same incomplete sentence twice. There is no wasted filler, but this is accidental duplication rather than deliberate conciseness.

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?

For a tool with a nested-object input and no output schema, the description should explain the expected input payload and the shape of the audit result. Instead it trails off, leaving the agent to guess both what to supply and what comes back.

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 nominally 100%, but the sole parameter is an opaque nested 'input' object whose only documentation is a link to the Apify listing. The description adds partial meaning by indicating the input should be a Google Maps scraper dataset with the business plus local competitors, but leaves the actual payload shape unspecified.

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 names a concrete outcome (an AI local SEO audit covering profile completeness gaps and review strategy) from a Google Maps scraper dataset, which is more than a restatement of the title. However, the text is visibly truncated mid-sentence twice ('your business + local…') and never distinguishes it from nearby siblings like google_maps_lead_enricher, google_reviews_insights, or ai_seo_site_auditor.

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?

The only usage cue is 'Point it at any Google Maps scraper's dataset,' which describes the input rather than when to choose this over alternatives. No prerequisites, no exclusions, and no mention of the sibling tools that overlap on Google Maps or SEO auditing.

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