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

Annotations only declare the safe read-only profile; the description goes well beyond them by disclosing the return payload (connect_url), the out-of-band approval flow through Instagram and saypage.ai, and the explicit permission boundary (no publishing rights requested). That is exactly the context an agent needs before invoking.

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 short sentences, front-loaded with the action and the returned value, then the follow-up step, then the scope caveat. Every sentence carries operational information with no filler.

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, so return values need not be enumerated, yet the description still names the one field the caller must act on. Combined with the next-step pointer to get_account, an agent has everything needed to run this tool correctly.

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 and schema coverage is 100%, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly spends no words on parameters.

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 and resource ('Start connecting the user's Instagram professional account') and scopes it to the professional account type. It is clearly separable from siblings like prepare_instagram_post or get_instagram_publishing_link, which it names.

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?

Gives the full usage sequence: call this, hand the returned connect_url to the user verbatim, wait for the Instagram approval round-trip, then call get_account. It also explicitly rules out a nearby concern ('This never asks for permission to publish posts') and routes that need to get_instagram_publishing_link.

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