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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds workflow-level behavior the annotations cannot: this is the prerequisite step for account-scoped tools, it surfaces connection status and a tokenStatus of unauthorized, and it instructs the agent to ask the user rather than pick an account. That is meaningful context beyond the structured safety hints.

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 core directive (call this first) is front-loaded and every sentence carries routing information. The parenthetical listing five feed tools is dense and slightly bloats the middle, but it does prevent a real misrouting error, so the cost is defensible rather than wasted.

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?

An output schema exists, yet the description still names the returned fields (accountId, username, display name, connection status, time zone), which tells the agent what can be read off the response without opening the schema. Combined with prerequisite and multi-account guidance, nothing an agent needs is missing for this zero-param list tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Its discussion of accountId refers to downstream tools' requirements rather than this tool's input, which is useful orientation but not parameter semantics here.

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 (lists) and a precisely scoped resource (Pinterest accounts connected to the user's Tailwind organization), plus the fields returned per account. It is distinguishable at a glance from siblings like list_feeds, get_account, and connect_pinterest_account.

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 to call this first because every account-scoped tool requires an accountId, names connect_pinterest_account for the connect/reconnect path, and carves out the org-scoped feed tools as exceptions while noting connect_feed does need an accountId. It even prescribes the behavior when multiple accounts come back and the user was ambiguous.

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