get_gmvmax_campaign_info_tool

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions the endpoint path but does not explicitly state that this is a read-only, idempotent operation (though it is implied). No contradictions.

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 at two sentences, front-loaded with the action and endpoint, followed by a list of return details. Every sentence adds value without fluff.

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?

Given the tool's simplicity (2 required string params, output schema present), the description adequately covers the core functionality and return values. However, it could be improved by noting that it's a read-only operation or any constraints, but overall it is sufficient for the agent to select and invoke correctly.

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 description coverage is 0%, so the description must add meaning to the parameters. However, it only mentions the campaign ID implicitly via 'specific GMV Max campaign' but does not describe the advertiser_id or the format/usage of either parameter. The two required parameters are left to the agent to infer.

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 tool's purpose: 'Get detailed info for a specific GMV Max campaign' via a specific endpoint, and lists what information is returned (budget, bid, product, scheduling details). This distinguishes it from sibling tools like get_gmvmax_campaigns, which likely lists campaigns.

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 implies that you need a specific campaign to get info, but does not provide explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites or exclusions, leaving the agent to infer from sibling names.

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