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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true; the description reinforces this with "read-only proposal" and adds the important workflow constraint that changes must not be applied until the owner agrees. It does not describe the shape of the proposal or any rate/credit considerations, so it stops short of 5.

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?

Two tight sentences: the first defines the action and output, the second defines the safety workflow and target tools. No filler, and the read-only framing is front-loaded.

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 no output schema, the description adequately conveys that the return value is a proposal to be reviewed rather than an applied change, and it covers the safe follow-up path. It stops just short of describing how complete or structured the proposal is.

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 coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The description only loosely gestures at brand_id ("read the business") and says nothing extra about user_goal's purpose or privacy constraints beyond what the schema states.

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 sequence (read the business and connected social accounts) and the concrete output (who should post where, with examples of brand and founder profiles). It is clearly distinguishable from list_publishing_profiles and create_publishing_profile, and it names the sibling apply tools.

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?

Explicitly frames the tool as a proposal step whose result must be shown to the owner and only then applied via set_profile_accounts or set_linked_social_accounts, which effectively routes the agent to the right follow-up tool. It lacks a negative case (e.g. when an existing profile set makes this unnecessary), so not a 5.

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