social_media_posting_get_google_locations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. However, the description adds no additional behavioral context, such as what data is returned or any side effects. It provides zero value beyond the annotations.

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 extremely concise, consisting of just one phrase. It is not verbose, but it is under-specified, providing minimal structure or front-loaded context. It is efficient but does not convey enough substance to be considered well-structured.

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 should at least hint at the return value or typical usage. It does not mention what 'google business locations' refers to or what the caller receives. Given the tool's simplicity, some mention of a list of locations would improve completeness, but it is missing.

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?

The input schema fully documents both parameters (accountId and locationId) with descriptions, covering 100% of parameters. The description does not add any meaning beyond the schema, which is acceptable given the high schema coverage, but it also does not clarify how the parameters relate to the action.

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 'Get google business locations' clearly indicates the action of retrieving Google Business locations for an account. It uses a specific verb and resource, and is distinguishable from siblings like get_account or get_posts. However, it does not elaborate on the scope or any filtering, so it is clear but lacks differentiation details.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. An agent has to infer from the name and schema alone, which is insufficient for a tool with related siblings like set_google_locations.

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