meta_list_entities

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

Annotations already state readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that budgets are returned in minor units and shows the effective_status array format, but it does not mention pagination, ordering, permissions, or rate limits.

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 short and front-loads the core operation, then adds filter syntax and budget units. There is no filler, though the separate filter sentence is slightly less integrated than it could be.

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 the annotations, input schema, and output schema, the description provides enough context for a read-only listing call: what entities are listed, what status and budget data are returned, and how to filter status. It is not fully complete on pagination or limit behavior, but the remaining gaps are minor.

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%, so the description must compensate. It explains the entity_type values through 'campaigns, ad sets or ads' and gives effective_status examples, but leaves ad_account_id and limit undocumented.

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: list campaigns, ad sets, or ads in an ad account, including status and budgets. It is clear enough to distinguish this from a generic account listing, though it does not explicitly name sibling tools such as meta_get_insights or meta_list_ad_accounts.

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?

Usage is implied by the listing language and the effective_status filter example, but the description gives no explicit when-to-use or when-not-to-use guidance versus alternatives like meta_get_insights or meta_list_ad_accounts. There are no exclusions or prerequisite notes.

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