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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the read-only safety profile is covered. The description adds content-level context about what metadata is returned, but it does not disclose behavior beyond that, such as whether it returns a single campaign's metadata or how profile scoping works.

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 a single compact sentence that front-loads the resource name and uses a concise list of returned fields. It is efficient, though the missing verb makes it read more like a title than a clear instruction.

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 low-complexity read-only tool, the description is serviceable and lists key returned content. However, it leaves campaign_id semantics unspecified and does not clarify how this tool differs from the many sibling PPC tools, so an agent might not reliably select it.

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 describes profile_id but leaves campaign_id completely undocumented, and the description does not mention either parameter. With only 50% schema description coverage, the description should compensate by explaining what campaign_id means or whether it is required, which it fails to do.

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 identifies the resource (campaign metadata) and enumerates specific content areas (bidding strategy, placement settings, goal/KPI, tags, notes), making the tool's purpose fairly clear. However, it uses a noun phrase rather than an explicit verb and does not distinguish it from sibling tools like ppc_campaign_details or ppc_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 when to use the tool: when the agent needs campaign configuration and user metadata. It provides no explicit alternatives, exclusions, or conditions such as 'use ppc_campaign_details for performance metrics instead.'

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