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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that publishability is evaluated 'currently,' implying a live state check, but says nothing about refresh timing, caching, or result shape.

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 sentences, no filler. The capability summary comes first and the parameter-scoping rule second, which is the right order for an agent deciding whether the tool fits.

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 carries the return-value burden and does name the key fields (allowed media, text limits, publishability). It stops short of describing structure or granularity, but is sufficient to decide and invoke the 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?

Schema coverage is 100%, so the two parameters are documented, but the schema only says 'Optional account id'/'Optional provider filter' without resolving their interaction. The description supplies the missing semantics: pass one, the other, or neither for all accounts.

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 (get publish capabilities/provider rules for connected accounts) and enumerates the concrete payload: allowed media, text limits, publishability. This clearly separates it from list_accounts and the various get_instagram_* insight 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?

It explains how to scope the call (accountId for one, provider to filter, neither for all), which is useful selection context, but it never says when to reach for this over siblings like list_accounts or validate_schedule, and gives no when-not guidance.

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