bitbucket_list_workspaces_or_projects

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

With no annotations, the description carries the transparency burden. It explicitly states the read-only nature ('List'), specifies the return type as a JSON string, and discloses a ValueError condition for unconfigured clients. This is useful behavioral context, though it could further clarify empty-list 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 concise and well-structured: a one-sentence purpose, followed by 'Returns' and 'Raises' sections. No redundant wording; every sentence contributes necessary information and the main verb is front-loaded.

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 list tool with an output schema, the description is nearly complete: it covers purpose, return format, and error condition. A minor gap is not addressing the empty-list scenario, but this is not critical given the tool's simplicity.

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's scope ('all accessible') correctly implies no filtering arguments, and the schema already confirms no parameters, leaving nothing for the description to add.

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 'List' with a clear resource 'accessible workspaces (Cloud) or projects (Server/DC)', and the scope 'all accessible' adds precision. It distinguishes from sibling tools like bitbucket_list_repositories which list repositories, not workspaces/projects.

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 guidance is provided on when to use this tool versus alternatives. It does not mention sibling tools, prerequisites, or cases where this tool should be preferred, leaving the agent to infer usage from the name and context signals alone.

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