ghl_ad_google_entity_get

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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds endpoint details and OAuth scopes, which are useful for understanding access requirements. However, it does not disclose whether the response returns a list or single object, or how filtering works beyond the schema.

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 short (two sentences plus endpoint/scope lines). It is front-loaded with purpose. While the endpoint info may be unnecessary for AI agents, it does not significantly detract. Efficient and to the point.

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 9 parameters and no output schema, the description lacks important context about the response format (list vs. single), required relationships (e.g., locationId), and pagination. This gap could lead to misuse or extra trial-and-error queries.

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 coverage is 100%, so the baseline is 3. The description mentions 'based on entity type' which aligns with the schema's entityType parameter, but adds no additional meaning or context beyond what the schema already provides.

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 clearly states it retrieves Google campaigns, ad groups, or ads based on entity type. The title is null but the first two sentences specify the resource and action. However, the initial 'Get entities' is generic, and it does not differentiate from sibling tools like ghl_ad_google_campaign_get that target specific entities.

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 OAuth scopes as a prerequisite but offers no guidance on when to use this tool versus alternatives (e.g., ghl_ad_google_campaign_get for a single campaign). No when-not-to-use or comparison with sibling tools.

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