google_ads_upload_call_conversions

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

No annotations exist, so the description must fully disclose behavioral traits. It only states the upload action and parameter formats, but does not mention idempotency, duplicate handling, required permissions, error conditions, or side effects. This is insufficient for a mutation tool.

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 well-organized with an Args section, Returns note, and an example. It is reasonably concise, though the example is lengthy but provides necessary clarification for the nested structure.

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 adequately explains input parameters and return value, but lacks behavioral details (e.g., idempotency, error handling) and usage context. For a tool with no annotations and a complex nested parameter, it is functional but not comprehensive.

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 has 0% description coverage, leaving the description to explain parameters. It adds crucial semantics for call_conversions, including field names, format hints (E.164, datetime), optional fields, and an example. It does not detail customer_id or conversion_action_id, but their purpose is clear from context.

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 the action ('Upload call conversion data') and the resource ('phone calls that converted'). It distinguishes from sibling upload tools by specifying 'call conversions' as opposed to offline conversions, customer match, etc., though it does not explicitly contrast with them.

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 provided on when to use this tool versus alternatives (e.g., google_ads_upload_offline_conversions). There are no prerequisites, exclusions, or contextual hints about typical use cases.

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