list_workspaces

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

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly states that via an API key the result is always exactly one workspace, that archived workspaces are excluded, and that each entry includes billing_status to differentiate read-only from writable workspaces. These are meaningful behavioral nuances that go beyond a simple 'list' definition.

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 compact yet information-dense. Every sentence adds value: the result contents, the workflow context, the single-entry expectation, archived exclusion, and billing_status significance. No wasted words or repetition of schema information.

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 zero-parameter tool with no output schema, the description provides a remarkably complete picture: what data is returned, how to interpret unusual results, what is not included, and how to use a key field for operational decisions. It fully equips an agent to invoke and interpret results correctly.

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 tool has zero parameters, so the baseline is 4. The description appropriately focuses on output semantics rather than parameters, and no parameter explanation is needed.

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 tool lists the workspaces the API key can act in, including uuids, names, and the role held in each. It distinguishes itself from siblings by explicitly directing users to start here when they lack a workspace uuid and then proceed to list_boards, making the purpose and place in the workflow 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?

The description gives explicit when-to-use guidance: 'Start here when you do not already have a workspace uuid, then go to list_boards.' It also explains the normal single-entry result to prevent misinterpretation, and highlights billing_status to detect read-only workspaces before attempting writes, which is valuable contextual guidance.

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