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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real beyond-schema context: no authentication to the business is required, the data source is the Places API, and the return payload is described (score, ranked recommendations, reviews). It does not explain the non-idempotent lookup behavior declared in annotations, keeping it below a 5.

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 inputs, then a clearly flagged limitation in caps. No filler sentences; each clause adds distinct information an agent needs.

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 and only two optional parameters, the description still tells the agent what comes back, what data is used, whether login is needed, and what the tool cannot do. That is complete for this tool's complexity.

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 baseline is 3. The description adds semantics beyond the schema by stating the two parameters are alternatives ('query OR place_id') and that the tool is usable without login - information the schema fields do not convey.

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 ('Audit') and resource ('Google Business Profile'), and its deliverable (completeness score + ranked recommendations + recent reviews). An agent can distinguish it from siblings like get_audit, create_audit, or get_prospect_audit without opening any schema.

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?

Explicitly states the input paths (query OR place_id), the no-login/public-data condition, and an important scope boundary ('this tells you WHAT to fix; applying edits is not yet available'). It does not name a competing sibling to route away from, so it stops short of a 5.

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