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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds real behavioral context beyond them: the parameter is conditionally required, and a failed call returns an error enumerating the available workspaces by name, which tells the agent how to recover. It omits pagination/refreshed-ness details, keeping it 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?

Two tight sentences with no filler; the return-value inventory is front-loaded and the conditional parameter rule follows. Slightly clipped to the point of reading as a fragment, but nothing is 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?

With no output schema, the description does the work of previewing the response fields, which is the right instinct. But entries like 'capabilities' and 'readiness' are undefined, so an agent cannot tell what shape that data takes or whether the call is cheap enough to call routinely.

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, including the request_id tracing field. The description only restates the workspace_id conditionality, adding no new syntax, format, or default information, so the baseline of 3 applies.

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?

The description enumerates exactly what the call returns — role, readiness, plan, Creative Credits, account/post counts, capabilities — which distinguishes it from siblings like invoke_get_user_profile and invoke_list_connected_accounts. It is a noun list rather than a verb+resource sentence, but combined with the title the purpose is unambiguous.

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?

The description gives a conditional instruction for workspace_id ('pass when multiple workspaces exist') and reveals the fallback error behavior, which is useful. However, it never says when to reach for this tool versus invoke_get_user_profile, invoke_list_connected_accounts, or invoke_list_user_workspaces — usage is only implied.

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