get_advertiser_profile

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds behavioral context by specifying the return fields (name, verification status, ad counts by format, platforms), which helps the agent understand what data to expect.

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?

Description is concise with four sentences and bullet points. It front-loads the core purpose and then lists specific uses, making it easy to parse quickly.

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 simple two-parameter tool with no output schema, the description fully covers what the tool returns and its overall behavior. The annotations further reinforce safety, leaving no gaps for an AI to misunderstand.

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 coverage is 100% with descriptions for both parameters (advertiserId and region). The description does not add extra meaning beyond the schema, as it does not elaborate on parameter usage or constraints.

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?

Description clearly states verb 'Get' and resource 'summary profile of an advertiser's ad activity'. The bullet points detail specific outputs (verification status, ad counts, format distribution, platforms), effectively distinguishing it from siblings like get_advertiser_ads (which returns ad list) and search_advertiser.

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?

Description explicitly lists four usage scenarios with bullet points (e.g., 'Get an overview of a brand's advertising presence'). However, it does not mention when NOT to use this tool or compare it to alternatives among siblings, missing a chance to guide selection.

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