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

With no annotations provided, the description carries the full burden and does well: it discloses the authorization requirement (staff + manage), the valid range (1–50), null semantics (no workspace cap), and that line capacity and the deployment ceiling still constrain the result. It does not say whether the change takes effect immediately or how to revert it.

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 tight sentences with no filler, and the access constraint is front-loaded before the operational semantics. Every clause adds information an agent needs.

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?

For a two-parameter mutation with no annotations and no output schema, the description covers auth, value semantics, and interacting constraints. It omits the effect timing and any response/confirmation detail, which would fully close the gap.

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 description coverage is 0%, so the description must compensate, and it does for maxConcurrentCalls by explaining the 1–50 bounds and that null removes the workspace cap, plus interaction with other limits. workspaceId gets no explanation, but its uuid type and required status make its meaning self-evident.

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 states a concrete verb+resource: capping concurrent calls for a workspace across all its lines. It is clearly distinct from sibling mutators like platform_workspaces_suspend or platform_workspaces_reactivate. It stops short of explicitly naming an alternative tool, so a 4 rather than a 5.

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 gives a clear precondition for use: 'Platform staff only (account session). Requires manage.' This tells the agent who may call it and under what authority. It does not name alternative tools for adjusting capacity (e.g. lines_update), so it falls short of explicit alternatives.

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