ghl_ad_fb_reporting_list

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

Annotations already indicate readOnlyHint, idempotentHint, etc. The description adds endpoint and OAuth scopes, but these are standard and not critical for behavioral understanding. No disclosure of additional traits 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?

Description is concise with 4 lines covering purpose, endpoint, and OAuth scopes. It is front-loaded with the purpose. Minor improvement could be a more structured format separating purpose from technical details.

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 schema coverage and annotations, the description is adequate. However, no output schema is provided, and while the tool returns a list, the exact fields are not mentioned. Still, the context is sufficient for most usage scenarios.

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?

Input schema has 100% coverage with parameter descriptions, so the description adds minimal extra meaning. It restates that it returns a list, but that is inferred from the tool name.

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 it retrieves a list of Facebook campaigns, adsets, or ads with reporting data, using a specific verb and resource. It distinguishes itself from siblings like ghl_ad_fb_reporting_get which likely returns a single report.

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?

No explicit guidance on when to use this tool versus alternatives such as ghl_ad_fb_reporting_get or other list tools. The usage is implied by the type of list, but no exclusions or preferences are mentioned.

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