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

With no annotations, the description carries the full burden and delivers: it discloses stateful tracking across runs, conditional Slack side effects (only if the caller supplies a webhook/connector), required Apify auth, a 60 calls/min rate limit, and a pricing model. This is behavior an agent cannot infer from the schema.

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?

Front-loaded with purpose, then routing, then returns/side effects/auth/limits/pricing in scannable clauses. Dense but every sentence conveys a distinct operational fact; only the slogan 'your reputation radar' is filler.

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 an 8-param stateful actor with no output schema and no annotations, the description covers everything needed to call it correctly: statefulness, dry-run availability, alerting precondition, auth, rate limit, pricing, and the return shape (review objects flagged isNew with urgency scores).

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 100%, so the schema already documents query, maxPlaces, alertThreshold, dryRun, placeUrls, etc., and the baseline is 3. The description adds only marginal param context — the Slack-webhook-optionality and the isNew return flag — without restating the individual field meanings.

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 (monitor) and resource (Google Maps reviews) with a precise scope: only NEW reviews, stateful per business, with Bayesian urgency classification. It explicitly names the siblings it is not (google_maps_scraper, review_pitch_generator, local_presence_audit) and the condition that distinguishes each.

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?

Explicit when-to-use ('tracking review activity OVER TIME for businesses you already know') plus three named alternatives with the exact scenario each covers (one-shot bulk extraction, sales pitch from bad reviews, one-time presence audit). Nothing is left to inference.

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