social_media_posting_set_accounts

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

Annotations indicate readOnlyHint=false and destructiveHint=false, implying a mutating operation, but the description adds no behavioral detail. It does not state what gets modified, whether the operation is idempotent (idempotentHint=false), what side effects occur, or what the response looks like. With no output schema and sparse annotations, the description fails to disclose any behavioral traits beyond the bare action.

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 only two words, which is under-specification rather than conciseness. It does not front-load any actionable information and provides no structure. It fails to earn its place because it conveys nothing beyond the tool's name.

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?

This is a 7-parameter tool with 4 required parameters and no output schema, yet the description explains none of the purpose, flow, or constraints. An agent cannot correctly invoke this tool based on the description alone, especially given the broad sibling toolset. The description is completely inadequate for the tool's complexity.

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 86%, so the parameters are well documented in the schema itself. The description adds no parameter-level meaning, but since coverage is high, the baseline of 3 applies. The description does not harm, but it also provides no additional clarification for ambiguous fields like 'accountIds' or 'rowsCount'.

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 'Set Accounts' is a verb+resource but extremely vague. It does not specify what kind of accounts, what 'set' means (assign, configure, activate?), or how this differs from sibling tools like social_media_posting_attach_facebook_page_group or social_media_posting_set_google_locations. The title and description are nearly identical, so it reads close to a tautology and fails to convey a distinct purpose.

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 versus alternatives. No context, prerequisites, or exclusions are mentioned. The description gives an agent no basis for deciding to call this tool over any other in the social_media_posting family.

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