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

Annotations already declare readOnlyHint and destructiveHint. The description adds 'snapshot read' but this mostly reinforces the read-only nature without introducing new behavioral details like permissions or side effects.

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 a single, concise sentence that conveys the essential information without unnecessary words. It is well-structured and easy to parse.

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?

For a simple read-only tool with one parameter, the description covers the core functionality. It does not detail the return format, but that is not required given the simplicity and the presence of an output schema. Slightly more context about the eligibility criteria could be added, but it is sufficient.

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 only parameter, ad_account_id, is self-explanatory but lacks a formal schema description. The description's mention of 'one ad account' provides minimal clarity. Since schema coverage is 0%, the description partially compensates but does not fully explain the parameter's format or purpose.

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 action (List), the resource (pages eligible for ad creation), and the scope (on one ad account). It distinguishes this from sibling tools like 'assets_list_pages' by specifying the eligibility criterion and account context.

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 mentions 'snapshot read' but does not explicitly state when to use this tool over alternatives such as 'assets_list_pages'. The context is implied but not directly compared to other listing tools.

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