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

Annotations already cover the safety profile (readOnly, non-destructive, closed world), so the bar is lower; the description still adds real context by disclosing the return fields and the plan/allowance behavior ('what bounds a free-plan profile is its monthly post allowance, applied when posts publish'). It does not cover pagination or limits on profile count, keeping it just short of a 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?

Three front-loaded sentences with no filler: purpose/scope, the ordering directive plus consumer tools, then the plan caveat. Every sentence carries operational information.

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 compensates by listing the returned fields, and it supplies the sequencing and quota semantics an agent needs. Nothing required to select or invoke this tool 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?

Zero-parameter tool, so the baseline is 4. The description goes slightly further by naming the downstream profileId parameter the returned value feeds into, which is meaningful guidance even though there is no input schema to elaborate.

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+resource ('List the Socialync profiles this connection can manage') and even enumerates the returned fields (id, name, default flag, connected-platform count). The 'profiles' resource is cleanly distinct from sibling list tools such as list_connections and list_audiences.

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 says 'Call this first when posting' and names the four downstream tools (publish_now / publish_scheduled / create_post_draft / schedule_post_draft) that consume the returned profileId. The condition for using it and the alternative path are both spelled out.

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