run_full_audit

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: 6-10 free web requests, ~10-30 second runtime, and that it returns every finding plus a prioritized leak list. It does not mention failure/partial-result behavior or rate limits, but the cost, latency, and external-request profile are exactly the context an agent needs before invoking an expensive orchestrator.

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 purpose, scope, and cost are front-loaded in the first paragraph, and the Args block adds semantics rather than restating the schema. It is a touch long and the Args formatting is slightly verbose, but nearly every line earns its place.

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?

An output schema exists so return values need not be explained, yet the description still summarizes the return ('every finding plus a prioritized leak list'). Scope, cost, and all four parameters are covered; only error/partial-failure handling and explicit sibling routing are absent, which is minor.

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 0%, so the description must compensate, and it documents all four parameters with real semantics: business and city include concrete examples, trade explains it is guessed from the name when omitted, and website_url explains that providing it skips discovery. This adds genuine meaning beyond the bare string types and empty-string defaults in the schema.

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 concrete verb ('Run') and resource (the complete lead-leak audit) and enumerates the exact dimensions covered: search presence, website hygiene, form platform, tap-to-call, NAP consistency, and top-3 competitors. The word 'COMPLETE' plus 'full methodology used in real paid audits' cleanly separates it from the granular siblings like check_form_platform and audit_website.

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?

Usage is implied rather than stated: the agent infers this is the comprehensive option versus the piecemeal sibling checks, and website_url is noted as skipping discovery. However there is no explicit when-not-to-use guidance (e.g. 'use check_nap_consistency for a single check') and no note on whether it is safe to run repeatedly. Context is present but routing 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.