list_google_ads_links

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes a read operation (returns a list) but does not mention side effects, authentication requirements, rate limits, pagination behavior, or any limitation on the number of links returned.

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 with two sentences. The first sentence immediately states the purpose, and the second addresses the parameter format. No redundant or filler content.

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?

The description covers the parameter format adequately, but fails to describe the return value structure (e.g., what fields are in each link object) or any pagination/limits. Given no output schema, the description should provide more to be fully 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?

The schema provides only type info (integer or string) for property_id with 0% coverage. The description adds crucial format details: accepted formats are a number or a string 'properties/' followed by a number. This adds meaningful guidance beyond the schema.

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 'Returns a list of links to Google Ads accounts for a property' which specifies the verb (returns), object (list of links), and resource (Google Ads accounts for a property). It distinguishes this tool from siblings like get_account_summaries and run_report.

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 no guidance on when to use this tool versus alternatives such as get_account_summaries or other list tools. It does not mention prerequisites, connected Google Ads accounts, or cases where the tool is applicable or inapplicable.

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