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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description does add real behavioral value by disclosing the empty-state contract: a location with no profile yields `audit` as null with a `note` explaining what to set up. It stops short of covering freshness (how recent the audit run is) or whether a run is triggered on call.

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?

Purpose is front-loaded in the first clause, followed by return contents and then the null-audit edge case in a natural order. The long parenthetical field list is dense but informative rather than redundant; only minor trimming would be possible.

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 carries the return-value burden and does so thoroughly, including the important null/`note` branch. It is close to complete for a single-parameter read tool; only recency/staleness of the audit and whether results are cached are unaddressed.

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?

With one parameter at 100% schema description coverage, the schema fully documents location_id and its provenance. The description adds no constraint, format, or edge-case meaning for the parameter beyond what the schema supplies, so the baseline of 3 applies.

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 and resource: "Read a location's Google Business Profile Audit," and enumerates the audit's contents (profile data, NAP check, local ranking factors). It is clear what the tool returns, though it never names the sibling tools (e.g. get_local_search_grid_report, get_rank_tracker_report) whose output could overlap with the ranking-factor and per-keyword rank data described here.

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?

There is no explicit guidance on when to reach for this tool versus the several adjacent report tools (get_rank_tracker_report, get_local_search_grid_report, get_location). Usage is only implied by the resource name. The single routing hint — location_id coming from list_locations — is already in the schema, not new guidance.

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