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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly states 'This never retries or changes Google Ads,' which is a valuable non-mutation guarantee. It also indicates the receipt is tenant/customer-bound. It does not discuss error behavior or whether receipts expire, but the read-only assertion is strong and clear.

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 two concise sentences, front-loading the core action and resource in the first sentence and adding the key non-mutation behavior in the second. Every word earns its place, with no redundant filler.

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 read operation with only two parameters and no output schema, the description covers the essential purpose and safety profile. It could be slightly more complete by explaining what a lifecycle receipt contains or how it relates to prepare/confirm flows, but the agent has enough to select and invoke the tool correctly in most cases.

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 covers customer_id with '10-digit Google Ads customer id,' but draft_id has no description. The tool description indirectly clarifies that draft_id refers to a native Google mutation draft, adding some domain context. However, it does not explain how to obtain draft_id or any format/lifecycle details, leaving a partial gap at 50% schema coverage.

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 a specific action ('Read') and a specific resource ('tenant/customer-bound lifecycle receipt for one native Google mutation draft'). It also explicitly distinguishes itself from mutation/retry tools by saying it never retries or changes Google Ads, which separates it from siblings like google_ads_mutation_reconcile.

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 makes clear this is for reading a receipt for a single mutation draft and that it does not retry or change anything. However, it does not explicitly name alternative tools or state when to prefer this over related tools such as google_ads_mutation_reconcile or task_get. The guidance is implied rather than explicit.

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