businesses_get_businesses_by_location

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description does not need to repeat those. However, it adds no extra behavioral context such as return format, pagination semantics, or that it returns a list. The description is essentially a paraphrase of the tool name and provides no incremental transparency.

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 description is a single short phrase 'Get Businesses by Location' that essentially restates the tool name. While it is concise, it fails to provide additional useful information, so the brevity is not warranted—it is under-specification rather than effective conciseness.

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 tool with three parameters, no output schema, and several closely related siblings, the description is severely incomplete. It lacks any mention of return value, pagination controls, default limits, or how it differs from 'businesses_get_business'. An agent would have to guess many aspects of how to call it correctly.

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 low (33%)—only locationId has a description. The tool description does not explain the skip and limit parameters at all, leaving their purpose and use ambiguous. It only mentions 'location', which aligns with locationId, but provides no details on pagination or required versus optional parameters.

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 the verb 'Get' and the resource 'Businesses' with a location filter, which clearly indicates a retrieval operation. It is distinguishable from the sibling 'businesses_get_business' which likely gets a single business, though it does not explicitly point to that sibling.

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?

No guidance is given on when to use this tool versus other business-related tools, nor does it mention pagination behavior, default limits, or any context that would help an agent decide to call it. The description is purely declarative without any usage instructions.

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