List Connected Accounts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with a read-only 'List' verb. It adds meaningful behavioral detail beyond annotations: the exact return shape, that Facebook page accounts go in pageIds, that no arguments are accepted, and that downstream tools require these ids rather than usernames. No contradiction exists.

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 compact and front-loaded: it states what the tool returns first, then gives usage prerequisites and exclusions. Every sentence adds actionable information; there is no filler or repetition of schema 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?

For a zero-argument read-only list tool, the description is complete: it covers the return value, field semantics, when to call it, how to place ids in the correct arrays, and which sibling tools should be used for other needs. The output schema further covers return structure, so nothing essential is missing.

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 tool has zero parameters and the description explicitly states 'Takes no arguments', leaving no ambiguity about invocation. With no parameters to document, the description fully covers parameter semantics.

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?

States a specific verb ('List'), a clear resource ('social accounts'), and scope ('across all nine platforms'). It also differentiates itself from siblings by explicitly saying it is not for post history or publishing status, naming list_posts and list_post_results as the correct alternatives.

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?

Provides explicit when-to-use guidance: 'Call this before create_post, update_post, or bulk_schedule_posts'. It also gives a precise exclusion — 'Not for post history or publishing status: use list_posts or list_post_results for those' — so an agent knows exactly when not to choose this tool.

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