get_account_pages

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

The description notes the optional access_token and caching behavior, adding some behavioral context beyond the schema. However, it lacks details on authorization requirements, rate limits, or error conditions, which are important for safe invocation.

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, using a clear structure with Args and Returns sections. Every sentence serves a purpose, and it is front-loaded with the core verb and resource.

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 presence of an output schema, the description reasonably omits return value details. However, it misses authentication context (e.g., token scopes) and pagination information, which could be relevant for a complete understanding.

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?

With 0% schema description coverage, the description compensates by explaining the account_id format (act_XXXXXXXXX) and the access_token's optional caching behavior. This adds significant meaning beyond the schema's type definitions.

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 pages associated with a Meta Ads account, specifying the verb 'Get' and resource 'pages'. While it distinguishes from siblings like search_pages_by_name or get_ad_accounts, it does not explicitly differentiate, but the context is sufficient.

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 guidance is provided on when to use this tool versus alternatives like search_pages_by_name or get_account_info. There is no mention of when not to use it or prerequisites, leaving the agent without explicit direction.

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