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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that results include both top and worst performers, which is useful ordering context. It does not explain what limit does, whether results are truncated, or anything about the return shape, leaving gaps beyond annotations.

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?

Two sentences say substantially the same thing: 'Rank ... by a metric' and 'Get top and worst performing ... ranked by a metric.' The quoted use cases are helpful, but the repeated ranking statement wastes space and the description is not front-loaded with anything beyond the purpose.

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?

With no output schema, five parameters, and only 60% schema coverage, the description should do more to explain limit, date_preset, and the campaign-level option. It is adequate for understanding the tool's purpose but not complete enough to invoke it confidently without inspecting the schema.

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 only 60%: limit and date_preset have no schema descriptions, and the description does not compensate for either. It does mirror the metric-ranking idea, but it also says 'ads or ad sets' while the level enum includes campaign, creating a mismatch rather than clarifying the level parameter.

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 states a specific verb and resource: ranking a Meta account's ads/ad sets by a metric, plus the scale/cut framing. It does not, however, distinguish itself from the sibling get_platform_top_performers, so an agent cannot tell from this text alone which top-performers tool to pick.

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?

It offers implied usage via the quoted questions ("what is working", "what should I scale/kill"), which gives an agent a scenario. But there is no explicit when-not guidance, no named alternatives (e.g., breakdown tools or get_platform_top_performers), and no note on whether this replaces or complements get_platform_performance.

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