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

Beyond annotations, the description discloses that the tool is disabled until location edits are enabled, does not call Google while off, and omits business name/address/phone/website from results. These are meaningful behavioral and output-scope details not captured by readOnly/openWorld/idempotent hints.

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?

Four short sentences with the purpose front-loaded and no filler. There is minor redundancy between 'Stays off until location edits are switched on' and 'does not call Google while it is off,' but overall it is efficient.

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?

It covers the prerequisite and excluded output fields, which helps for a read-only tool with no output schema. However, it does not explain what 'attributes' or opening-hours results look like, and it leaves the single-location vs list ambiguity unresolved.

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 parameter documentation is already complete. The description only repeats 'Pass account_id or location_id' and does not add format, precedence, or behavioral meaning beyond 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?

The description states a specific action (read opening hours and attributes) and resource (Google Business location), but it says 'for one Google Business location' while the tool name/list semantics suggest listing locations. This mismatch leaves the core purpose somewhat ambiguous and does not distinguish it from siblings like list_accounts or manage_google_business_location.

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?

It gives a useful prerequisite ('Stays off until location edits are switched on') and suggests passing account_id or location_id, but it does not say when to use this tool instead of alternatives such as list_accounts or manage_google_business_location, nor what to do when the feature is off.

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