pfm_get_social_accounts

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds useful context about pagination and OR logic for filters, but it does not explain return format, default limit, ordering, or whether the 'connected' wording is restrictive despite the status filter allowing disconnected accounts.

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 two concise sentences, front-loaded with the main purpose, and every word earns its place. No fluff or redundancy.

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 moderately complex list tool with 7 parameters and no output schema or annotations, the description covers the essential aspects: pagination, filterable fields, and OR logic. It lacks information about return value structure or default behaviors, but it is sufficiently complete for a straightforward listing operation.

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 100% for all 7 parameters, so the baseline is 3. The description adds the general statement 'All filters use OR logic', which reinforces what is already in each parameter's schema description. It does not add significant new meaning beyond that.

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 'Get a paginated list of connected social accounts', specifying the verb (Get), resource (social accounts), and scope (paginated list). It distinguishes itself from the sibling tool pfm_get_social_account (singular) by implying list semantics.

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?

The description implies usage for retrieving multiple social accounts with filters, but it does not explicitly mention when to use this tool over the singular pfm_get_social_account or other alternatives. No exclusions or specific scenarios are stated, so usage guidance remains implicit.

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