List workspaces (EE)

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

No annotations are provided; the description only notes the Enterprise scope and API equivalence. It does not disclose pagination behavior, rate limits, authentication requirements, or what happens with the fetch_all parameter, leaving the agent with limited knowledge of the tool's behavior.

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?

The description is very concise, two sentences with no superfluous text. It is well-structured and gets to the point, though it could be slightly more informative without losing conciseness.

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?

Given the low complexity (one optional boolean parameter, no output schema), the description is adequate for basic use. However, it omits behavioral details like pagination and the meaning of 'Enterprise', which may confuse agents unfamiliar with the platform.

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?

The input schema covers the single parameter 'fetch_all' with a clear description. The tool description adds no extra meaning beyond the schema, which is sufficient but does not improve understanding of the parameter's effect or typical usage.

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 clearly states the verb 'List', the resource 'workspaces', and specifies it's for Enterprise. It also gives the equivalent API endpoint, making the purpose unambiguous and distinct from other Kong 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?

No explicit guidance on when to use this tool versus alternatives like kong_list or other workspace-related tools. The description implies a simple listing operation but does not provide conditions or exclusions.

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