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

With no annotations, the description carries the full burden and does disclose the auth requirement (staff/account session) and a privacy scope boundary ('No customer content'). It says nothing about pagination behavior, result ordering, or default result size, which matter for a list tool returning up to 100 rows.

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 with the hard access constraint front-loaded and zero filler. The telegraphic style is dense but every clause carries information; slightly more structure (rather than comma-stacked field lists) would make it easier to parse.

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?

Enumerating the returned fields effectively substitutes for the absent output schema, and the staff-only/session requirement covers the missing annotations' safety dimension. The remaining gap is that filter parameters, particularly status and the limit/offset pagination contract, are neither in the schema descriptions nor the prose.

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 0% for 4 parameters, so the description must compensate. It only clarifies the `query` parameter (workspace name or owner email); `limit`, `offset`, and the `status` enum filter are left entirely to the schema. Worse, 'status and limits' in the sentence reads as returned fields rather than filter inputs, which can mislead the agent about the status parameter.

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 the resource (every workspace) and enumerates the returned detail (owner, members, lines, 30-day calls and charges, status, limits), which separates it from the customer-facing workspaces_list and from platform_workspaces_get. No explicit verb, but the scope is unmistakable.

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?

'Platform staff only (account session)' is a concrete precondition that tells the agent who may call it, and 'Search by workspace name or owner email' states the intended lookup pattern. It never names the alternatives (platform_workspaces_get, platform_accounts_list) or states when not to use it, so it stops short of a 5.

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