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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that access is permission-scoped ("you can access") and that slugs and roles are returned, which is useful behavior beyond the annotations. It does not discuss pagination, formatting, or rate limits.

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 tightly written sentences with no filler. Purpose is front-loaded, and the follow-up sentence immediately explains how to use the resulting slug without repeating structured data.

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?

There is no output schema, so the description must carry return-value context; it names the slug and the caller's role. Combined with annotations covering the safety profile and the routing advice for downstream calls, nothing important is missing for a no-parameter list tool.

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?

This tool has zero parameters, so the baseline is 4. The description references a `workspace` argument, but only for downstream sibling tools, not for list_workspaces itself, so it adds no relevant parameter semantics here.

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 uses a specific verb+resource ("List the APIMock workspaces") and scopes it to "workspaces you can access." It also states the returned key fields (slug and your role), making the tool distinguishable from endpoint, folder, resource, and fault-rule siblings without opening a schema.

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 clearly tells the agent what to do with the result: pass the slug as the `workspace` argument to list_endpoints / create_endpoint. That gives strong usage context, but it stops short of an explicit when-to-use/when-not statement or naming any alternative workspace listing route.

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