ghl_ad_google_conversion_goal_list

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

The description aligns with annotations (readOnlyHint=true, etc.) and adds useful behavioral context like the specific OAuth scope required ('adPublishing.readonly'). It does not contradict annotations. While the description could mention the non-destructive nature, annotations already cover that.

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 concise, starting with a clear purpose statement followed by essential technical details. Every sentence adds value (purpose, endpoint, version, scopes). Could be slightly more structured but 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?

For a simple list tool with two parameters and no output schema, the description covers the essential: locationId, optional isDraft, and required scopes. However, it does not mention that the tool returns a list of conversion goals, pagination behavior, or any result structure. Adequate but could be more complete.

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?

Input schema coverage is 100%, so baseline is 3. The description does not add meaningful semantics beyond the schema: 'locationId' is described as 'Location identifier' and 'isDraft' as 'Is draft'. No elaboration on the meaning of 'isDraft' in this context. No additional value.

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 Ads conversion goals for a location. The verb 'Get' and resource 'conversion goals' are specific. However, it does not explicitly differentiate from sibling tools like ghl_ad_google_conversion_list or ghl_ad_google_conversion_get, which might cause confusion for an AI agent.

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 endpoint details and OAuth scopes but offers no explicit guidance on when to use this tool versus alternatives. It implies usage for listing conversion goals but lacks exclusions or context about preferred scenarios.

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