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

No annotations are provided, so the description carries the full behavioral burden. It never discloses the reporting time window (there is no date parameter at all), whether metrics are aggregated or time-series, data freshness, or required permissions — all critical for an analytics tool. Read-only is only implied by 'Get'.

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?

A single front-loaded sentence with zero filler; the metric list is the most useful part and appears early. It is not padded, though its brevity is also the source of the gaps elsewhere.

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?

No output schema, no annotations, and 0% parameter documentation leave the description as the only source of information, yet it omits the reporting period, response shape, and bot_id's role. For an analytics tool where the time window defines the meaning of the numbers, this is a substantial omission.

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% for both parameters. The description names 'campaign', which loosely maps to campaign_id, but bot_id is entirely unexplained and no format, scoping, or relationship between the two IDs is given. With two undocumented params the description must compensate and does not.

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?

States a specific verb ('Get'), a specific resource ('performance metrics'), enumerates the metrics returned (impressions, clicks, CTR, conversions), and scopes them to a campaign. This distinguishes it from get_bot_performance_scorecard and get_help_center_analytics by resource, though it never names those siblings explicitly.

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 statement of when to use this versus get_bot_performance_scorecard, get_help_center_analytics, or get_dashboard_screenshots, and no prerequisites or exclusions. Only the implicit signal that a campaign_id is needed hints at context.

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