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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description's only added behavioral signal is the word 'interactive', with no detail on what is returned, whether it triggers a UI, or how date/account scoping behaves.

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 single sentence is clean and front-loaded with no filler, so it is technically concise. But its brevity reflects under-specification rather than efficiency, given the tool accepts seven parameters.

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 tool with seven optional params, a date_preset enum, and a substantial sibling set, the description is far too thin. It omits parameter meaning, usage conditions, and any behavioral detail beyond what annotations and the output schema already encode, so an agent lacks enough to invoke it confidently.

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% across 7 parameters (since, until, date_preset, campaign_ids, ad_account_id(s), connection_context), so the description must compensate and does not mention any parameter at all. Neither the schema nor the description tells the agent what these fields mean or how they interact.

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 pairs a verb ('Show') with a resource ('interactive ads console'), so the basic action is identifiable. However, it never explains what 'interactive console' means or how this differs from siblings like open_ads_console, render_performance_report, or render_ad_previews, leaving the agent unable to distinguish it.

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?

There is no indication of when to use this tool versus open_ads_console or the other render_*/console_* tools, and no prerequisites or context described. The agent gets only a one-line purpose with no routing guidance.

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