List locations of an account

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

Annotations already declare readOnlyHint and destructiveHint, covering safety. The description adds valuable behavioral details: totalSize presence depends on filter, fields are controlled by readMask, and metadata must be requested for mapsUri/placeId/newReviewUri. This goes beyond annotations without contradicting them.

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?

Three sentences, each earning its place: purpose, id linkage, and conditional behavior. Front-loaded with the core verb and resource, no fluff or redundant restatement.

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 a list tool with no output schema, the description covers key caveats: id naming convention, totalSize condition, readMask effect, and metadata fields. It does not explicitly describe pagination behavior or default values, but the schema documents pageToken and pageSize defaults. Overall fairly complete for the 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% for all 6 parameters, so baseline is 3. The description adds some context about how the response id feeds locationId elsewhere, but this is output-related rather than param-specific. It reinforces readMask guidance already in the schema but doesn't materially extend parameter understanding.

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 opens with 'Lists the business locations under an account', a specific verb+resource that clearly differentiates from siblings like get_location or list_accounts. It also states the API context (Business Information API) and explains how the returned id feeds other tools, further clarifying its role.

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?

The description provides context on when to use this tool: to get location IDs that feed locationId elsewhere (Performance API, reviews/posts). It also notes that totalSize only appears with a filter and that readMask limits fields, guiding usage. It does not explicitly name alternatives or say 'when not to use', but the guidance is clear.

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