Meta ad performance metrics

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description reinforces the read-only nature by stating 'Read-only' and adds context that the tool requires a connected ad account. While it doesn't detail rate limits or error cases, the combination is sufficient.

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 concise, with three sentences that front-load the core purpose. Every sentence adds necessary information without redundancy.

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?

The tool has 6 parameters and an output schema. The description covers all parameters and hints at return fields, but lacks details on pagination or limits. Given the annotations and schema, it is reasonably complete.

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 input schema has 100% coverage with descriptions for all parameters. The description adds value by grouping parameters (e.g., 'Date window: datePreset ... OR since+until') and clarifying the role of adAccountId for authentication. It also mentions the default for datePreset.

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 clearly states the tool pulls performance insights for Meta ad accounts, campaigns, ad sets, or ads. It lists specific metrics (spend, impressions, etc.), distinguishing it from sibling tools like search_meta_ads or list_meta_ads which likely have different focus.

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 explains parameter usage (adAccountId required, optional objectId, level, date window) but does not explicitly state when to use this tool over alternatives. It implies it's for retrieving performance data, but lacks guidance on when not to use it.

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