pfm_update_social_account

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

No annotations are provided, so the description is the only source of behavioral information. It does not disclose whether updates are partial or full, whether username and external_id can be updated together, idempotency, error conditions, or any side effects. This is a significant gap for a mutation tool.

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 clear sentence that is easy to parse and front-loads the action and resource. It is appropriately concise for a simple update tool, though it lacks depth in other areas.

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?

With three parameters, no annotations, and no output schema, the description is insufficiently complete. It does not explain expected outcomes, partial update behavior, or any constraints. For a straightforward API, basic info is present, but the lack of behavioral details makes it incomplete.

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%, so each parameter is already described. The description adds 'username or external_id,' reinforcing the two updateable fields, but does not clarify if both can be supplied simultaneously or if they are mutually exclusive. It meets the baseline but adds little beyond the schema.

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 ('Update') and the resource ('a social account'), and specifies the two fields that can be updated ('username or external_id'). It distinguishes from siblings like create or disconnect, though it doesn't explicitly mention it only updates these fields and not others.

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?

There is no guidance on when to use this tool vs alternatives such as create_social_account or disconnect_social_account. The description simply states what it does without any context, prerequisites, or exclusions.

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